Re: working on multiple patches

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 goal is. I don't necessarily need all the history in my
local repository. It is to be used only for creating patches, like patch
B in my first example. The remote repository is really big and I would
like to minimize traffic from it.

Thanks in advance
Jarek

Thorsten Schöning pisze:
> 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 you like. The is different in
> Subversion, as it is a centralized system.
>
> Mit freundlichen Grüßen,
>
> Thorsten Schöning
>
>
Received on 2011-11-14 10:11:41 CET