[Lazarus] Lazarus repository in Git (summary)

Graeme Geldenhuys graemeg.lists at gmail.com
Thu Nov 6 10:20:57 CET 2008

On 11/6/08, Michael Van Canneyt <michael at freepascal.org> wrote:
>  I considered Git for use in my company, (subversion is quite bad for
>  handling lots of banches) and frankly: I decided against it because
>  people here couldn't understand it.
>  They have a hard time understanding Subversion (or CVS or any of it),
>  and git is even 2 notches harder to understand.

That I understand all to well. We had the same issue when we moved
from Team Coherence to SubVersion. SubVersion could really do with a
GUI like TC has. Anyway the "hard to understand" issue was easily
resolved by writing a short 1 page summary of the most common commands
they would need for every day work. Then as they get familiar with the
tool after a few months, we started introducing them to new commands
(if needed).  We also setup a "sandbox" repository for them to
experiment in - they really liked that. :)

> That and the fact that
>  there is no decent GUI clinched the matter.

I know of two and a few in the pipe-lines. But then, I'm a CLI guy.
Anyway, I also found a very nice site showing the SubVersion commands
on one side and the Git commands on the other.  Most Git commands
where shorter and quite easy to understand.  But yes, as with any
other tools, there will be a period containing a learning curve.

>  Sometimes one must weigh the technical features against practical usage.

True. I must say, I'm very impressed with "svnmerge.py" tool. I have
been playing with it for the last 30 minutes. It makes SubVersion
branching much easier! I've always avoided branching in SubVersion
even though branching is very handy, simply because it is overly
complex. Git makes this as simply as pie (out of the box).

  - Graeme -

fpGUI - a cross-platform Free Pascal GUI toolkit

More information about the Lazarus mailing list