git/darcs/bazzar
zippy
Thanks for setting this up. I'm also happily using devalot, would
also like to see it blossom. Lots of potential.
I'd love for you to shed your experience on which DSCM tool to use,
i.e. git vs. darcs vs/ bazaar. I'm ready to make the plunge, but from
what I've read bazaar is a much warm pool to jump into that git!
Thoughts?
-e
Christoph Kappel
famous of the three. I prefer Mercurial, because it's decentralized
and nothins has to be setup except a one-liner so create the initial
repository. It's local and the huge network overhead of subversion for
example is reduced to zero. Enough advertisment.
Actually I ever wanted to give git a chance, because it's pretty well-
spread and the feature to integrate patches is also nice. Mercurial
has extensions for thins kind of stuff and more as well. ;)
Peter Jones
> I'd love for you to shed your experience on which DSCM tool to use,
> i.e. git vs. darcs vs/ bazaar. I'm ready to make the plunge, but from
> what I've read bazaar is a much warm pool to jump into that git!
> Thoughts?
I'm currently experimenting with Git, and plan on playing with
Mercurial next.
From what I can tell, Mercurial is written in Python. I've never
really been a fan of Python, so it losses some points in my strange
way of judging things.
I know Git is popular, which is the main reason I'm giving it the
attention that I am. Does anyone else feel strongly about a
distributed version control system?
To be honest, I really like Subversion, everything except branching
and merging (which is why I've written a few wrappers around it). But
I completely see the value in using a distributed version control
system with open source projects. It's a godsend really.
--
Peter Jones
http://pmade.com
Sam Lown
of the popular distributed version control systems and after some
comparison decided that git had the ideal combination of speed and
installation ease. Its so incredibly fast, and really does just get
out of your way.
Another thing that put me off the other distributed systems is that
they use scripting languages, Python mainly. While this isn't
necessarily a bad thing, certainly a lot more portable, I really don't
need to worry about managing more dependencies on versions of Python.
Gem is a sufficient pain in the ass for me.
The only negatives I found against git, was the apparent lack of
support for Windows (not that I use it!). However, having recently
installed the mini-cygwin version on a few Windows machines my fears
went out the window. It worked great!
Finally, although biased towards git, I'm easy and as long as its an
"apt-get install" away, I'll be happy :-)
sam
Peter Jones
> The only negatives I found against git, was the apparent lack of
> support for Windows (not that I use it!). However, having recently
> installed the mini-cygwin version on a few Windows machines my fears
> went out the window. It worked great!
The only bad thing I can say about Git so far is the verbose output
from commands like git status. It's probably from using CVS and
Subversion for 10 years, but I find myself scanning the output of git
status trying to figure out what it's saying.
I'm hoping to find the time to write a gitk like interface for Emacs ;)
Christoph Kappel
a really long time - but actually never wrote a single line in Python.
The syntax is sometimes really scary and many programs written in
Python have a horrible performance. So it's easy to have prejudices
against it - understandable though.
I read about Mercurial and spend some time digging into it. Later I
wanted to extend Mercurial with an extension and that was my entry
point. It has it's use and development with it is really straight
forward - Ruby is nice too. Can't say which one I like more. ;)
There are just some really cool programs written in Python.
(Mercurial, SCons)
Steve Knight
'right' there's no reason why it should be horribly slower than
anything else for this sort of task. But that's kind of off-topic!
I just wanted to pick a DSCM tool to play with and figured Git would
be a good place to start. Thanks for the pointers!