Re: working on multiple patches

2011-11-14 Thread Jarek Czekalski
:53AM +0100, Jarek Czekalski wrote: Jedit is maintained as an svn repository. I have read only access to it. I mentioned hg only because I got in touch with it in another project. I would like to stay with bare svn, as hg generated patches may differ in format. I would recommend using hg

Re: working on multiple patches

2011-11-14 Thread Jarek Czekalski
Jedit is maintained as an svn repository. I have read only access to it. I mentioned hg only because I got in touch with it in another project. I would like to stay with bare svn, as hg generated patches may differ in format. Andreas Tscharner pisze: I see. Could you please help me establish a

Re: working on multiple patches

2011-11-14 Thread Jarek Czekalski
ze: Guten Tag Jarek Czekalski, am Montag, 14. November 2011 um 08:13 schrieben Sie: Is Mercurial simply better in this case? Yes, because with every clone, or however it is called in hg, in distributed version control systems you always have your own copy of a repository which you can work

working on multiple patches

2011-11-13 Thread Jarek Czekalski
Hi I finished working on a patch A and posted it to acceptation. I would like to keep this patch applied in my working copy and work on another patch B. I don't see any way to do this, except having my own svn repository. But with Mercurial it was easy: 1. Revert all 2. Apply patch A throuch