2011/11/14 Thorsten Schöning :
>
> If hg doesn't fit, it sounds like vendor branche sin SVN would fit
> most:
>
> http://svnbook.red-bean.com/en/1.5/svn.advanced.vendorbr.html
>
Or for just a few instances, you can copy your svn working copy to
keep different states and you'd have the ability to r
Guten Tag Jarek Czekalski,
am Montag, 14. November 2011 um 10:11 schrieben Sie:
> I see. Could you please help me establish a scenario with a local svn
> server? I don't know what are the best ways to achieve the following:
If hg doesn't fit, it sounds like vendor branche sin SVN would fit
most:
Stefan, it looks perfect. I also found a dedicated article for using hg
queues on svn repository.
http://mercurial.selenic.com/wiki/WorkingWithSubversion#With_MQ_only
Complete command line sequences are given there. I'll be trying it.
Stefan Sperling pisze:
On Mon, Nov 14, 2011 at 10:32:53AM
On Mon, Nov 14, 2011 at 10:32: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.
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
> I see. Could you please help me establish a scenario with a local svn
> server? I don't know what are the best ways to achieve the following:
Stupid question: Why do you want to use svn if you'll have a working system
with hg?
Concerning your problem: You might want to try to convert the main
I see. Could you please help me establish a scenario with a local svn
server? I don't know what are the best ways to achieve the following:
1. Clone current remote repository into local one
2. Update local repository to the latest remote version (reverting the
changes I did)
You know what my
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 on as yo
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
