[leafnode-list] Re: HEADS UP DEVELOPERS: leafnode-2 repository changed?to GIT (was?DARCS)

[Matthias Andree <matthias.andree@xxxxxx>]

clemens fischer schrieb am 2008-11-15:

> On Thu, 13 Nov 2008 07:12:07 +0100 Matthias Andree wrote:
> 
> > please note that I've migrated the repository from DARCS to GIT, to
> > overcome performance issues.
> 
> Your are talking about code browsing the darcs repo, right?  It is known
> that darcs has a well thougth-out theoretic foundation, but that its
> requirements on CPU power can explode in certain cases.  I'm a mercurial
> man, but I've always found darcs to be very user friendly.

True enough, but there are various "Git for DARCS" people websites that
show command equivalents, and quite detailed at that. I find that very
handy to just see the "git reset" variants without thinking too much.

Git merging and rebasing is something I have found inferior (in user
interface) to Mercurial. It will work, but its on-screen help is less
verbose, if any.

Your current Lua branch is still in DARCS, and will remain there until I
merge (with the showstopper being the FreeBSD PCRE<->Lua build issues
for the nonce).

> Git is a beast in the number of commands needed to operate a repo,
> I sure hope I'll manage.  Then again, with the huge count of git repos
> out there, git knowledge is a must.

Git is really fast, and gitk is a nice tool to inspect repositories.

It seems that Git->Mercurial conversion isn't that bad, and I
managed to install the Hg fast-import extension, and Miklos Vajna's
darcs-fast-export seems to be one of the tools that do their job well.
Miklos also has patches for Hg fast-import.

Given that Mercurial is also quite swift (with Bazaar a long way behind
either of Git/Mercurial) and seems a bit better integrated rather than a
huge pile of tools, Git may not be the final word on the repo.

If the pain becomes too large and Git development were not to catch up,
I might switch again, but let's try it for a while - after all, Git is
also undergoing development, and its user interface is in the
developers' focus. At the Git 1.1 times, it would certainly not have
been an option.

-- 
Matthias Andree
-- 
_______________________________________________
leafnode-list mailing list
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
https://www.dt.e-technik.uni-dortmund.de/mailman/listinfo/leafnode-list
http://leafnode.sourceforge.net/