[dev-context] Wishlist / Tracker
mailing-lists.context-developers at rawuncut.elitemail.org
Mon May 30 23:51:19 CEST 2005
Hans Hagen wrote:
> Brooks Moses wrote:
> > happy with it. Part of my joy with it is because it's the first proper
> > version-control software I've used (well, ok, I tried cvs once, but
> > didn't get enough out of it to make it worth the bother), but it does
> > work exceptionally well at doing what I need -- namely, providing a
> > simple repository that I can use to synchronize working directories
> > between various computers with a minimum of bother, allowing me to back
> > up things with nearly zero trouble, and allowing me to occasionally
> > revert things to previous versions.
> do you have any experience with sychronizing two repositories?
This is a task that is incredibly easy to perform with either Arch or
darcs. In fact, it’s part of these SCM’s design to be able to do so.
Repositories are autonomous in these SCM’s. In subversion there’s only
one main repository, which makes it hard for people to hack the code and
send in patches. With Arch and darcs, all one needs to do is pull the
repository so that one has a local repository (repositories are
autonomous, remember?) and one can hack away. If one comes up with a
set of patches that one would like to see in the main-line development
(or the other way around - if you see patches that you would like to see
in the main-line) one can cherry-pick these patches into a change-set
(a set of patches) to be applied to ones own repository (e.g.,
I’m not doing either Arch or darcs justice, so I suggest that you find
more information on either of these for a better understanding of the
issues involved. The darcs manual is particularly easy to read,
Nikolai Weibull: now available free of charge at http://bitwi.se/!
Born in Chicago, IL USA; currently residing in Gothenburg, Sweden.
More information about the dev-context