I haven't tried any of the DVCS systems yet but I'm starting to
understand the deficiencies of Svn.
In the last article I've read about this they were recommending
Mercurial. They said Mercurial and GIT are very similar but Mercurial
has much better support for windows machines. Well, I'm on a Mac but
many are on windows. This article also says that Arch, Bazaar, Darcs
or SVK are not much used.
The biggest pain I have with SVN is when working on two branches at
the same time and always having to manually merge from one to the
other. I suppose that SVN 1.5 will be much better here.
Tool Support is another worry when thinking about switching.
- Hans
On Jun 5, 2008, at 6:36 AM, Ittay Dror wrote:
Russel Winder-4 wrote:
I strongly recommend using Bazaar. In a shared repository you
create a
mirror of the Subversion repository, then in the same shared
repository
you branch the mirror for you working branch. Then you have a local
mirror which is always buildable. You can even make corrections
such as
this one and then pull the changes into you working branch so as
to keep
it up to date. Then use rebase to realign the working branch to the
mirror.
I recommend using Git. It has great support for SVN and is very
popular
(linux kernel, x.org, wine, ruby-on-rails, to name a few). You can do
amazing things with it. In general I find that DVCS is great for
keeping a
clean history.
Here is a link to a presentation that explains Git's internals:
http://s3.amazonaws.com/chacon/git-talk.pdf
Ittay
--
View this message in context: http://www.nabble.com/can%27t-build-
from-svn-tp17601562p17661928.html
Sent from the gradle-dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email