[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: VCS (was: hurd-web/hurd/translator/unionmount.mdwn)

From: Sergiu Ivanov
Subject: Re: VCS (was: hurd-web/hurd/translator/unionmount.mdwn)
Date: Wed, 23 Sep 2009 17:54:54 +0300
User-agent: Mutt/1.5.20 (2009-06-14)


On Wed, Sep 23, 2009 at 04:01:36PM +0200, Arne Babenhauserheide wrote:
> Am Mittwoch, 23. September 2009 14:45:41 schrieb Sergiu Ivanov:
> > Well, yes, but wasn't CVS, for instance, created for distributed code
> > collaboration, too?  Or do I understand the word ``distributed''
> > wrong?
> The difference is that in CVS you have a reference server, so it's
> normally called "centralized", while in Git, Mercurial and Bazaaar
> every clone has the full history and you can synchronize with
> whomever you want - not only with the central server.

Yeah, I'm aware of this specific trait of CVS; I even think I once
heard that git, Mercurial, and Bazaar are called ``distributed'', but
I have already forgotten that :-(
> > A very nice map of differences, thank you :-) I'll use this mail as a
> > kind of reference for the future, if you don't mind ;-)
> It's only a list of examples :) 
> Here's a much nicer comparision, though a bit outdated (the comments
> bring it a bit up to date): -
> http://importantshock.wordpress.com/2008/08/07/git-vs-mercurial/
> "McGyver and James Bond" :)

Wow :-D I've got to read it :-) I'll do this tonight, I think.  Thank
you! :-)
> But I forgot two examples: 
> - Mercurial: History is seldomly rewritten and mostly considered as fixed. 
> - Git: History is rewritten often. 
> - Mercurial: A tag is simply part of a changeset and thus versioned as 
> everything else. 
> - Git: A tag is set by an authoritative source and outside version control. 

I see.  Thank you again :-)
> > > This also means, that scripts should always use the long version, because
> > > extensions can add commands, so an abbreviation can become ambigous when
> > > you add an extension (everything has its downside :) ).
> > 
> > Sounds complicated, but also like it shouldn't be extremely hard to
> > handle the problems once you know about them :-)
> It sort of automatically creates shorter aliases for you - saves keystrokes. 

Aha, so it does so automatically.  I somehow thought you have to
define aliases by yourself.
> And when you use an ambigous abbreviation, it tells you the ones from which 
> would fit. For example for me, "hg ch" says the following: 
> $ LANGUAGE=en hg ch
> hg: command 'ch' is ambiguous:
>     checkout chist churn

It's very much like bashcomp with git support enabled :-)

Though, of course explicit aliases are dominant when you define
non-prefix aliases (like checkout->update).
> (LANGUAGE=en keeps it from answering in german :) ). 

I have a course of German at the University now, so I'll soon become a
true Hurd man :-) (since, apparently, a lot of Hurd people speak
German).  I've already manage to plough my way towards understanding
the snippet about ``Zensur ist schön'' you add to your mails and I'll
hope I'll soon be able to read your stories in German :-)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]