From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Why's Git called Git ?
Date: Wed, 05 Jul 2006 21:33:33 +0200 [thread overview]
Message-ID: <e8h466$o4$1@sea.gmane.org> (raw)
In-Reply-To: 001001c6a06d$6e7b94b0$0200a8c0@AMD2500
Aaron Gray wrote:
> Anyway good going, I am glad Linux has an open source VCS again now.
>
> I do not know how BitKeeper are going to fell knowing they have been
> replaced by a Git :)
>
> I am toying with using a VCS for a set of related projects, either CVS
> because its well known, SubVersion for ease of use, or Git as it is new.
> Lots to descide upon, any pointers would be appreciated.
CVS is showing it's age; mainly the fact that IIRC it began as a series of
scripts over RCS, file level version control system, extending version
control to sets of files, somewhat. Branching in CVS is serious PITA.
Renaming _with_ retaining full and correct history: forget about it.
Subversion is "better CVS": still centralized, CVS infernal branching
replaced by "cheap copy" branching. Well known, replaces CVS thorough OSS
projects.
Git, Mercurial, Monotone, Bazaar-NG, Darcs are new brand of distributed VCS.
I really like notion of branching in Git; but be warned about tracking and
not recording renames, and the need of explicit packing (the latter very
minor). Powerfull, perhaps too powerfull for newbie user: but that is what
Cogito is for (although now Git contains fairly large set of high-level
commands).
http://git.or.cz/
http://git.or.cz/gitwiki
http://git.or.cz/gitwiki/Git
and "Other version control software" at
http://git.or.cz/gitwiki/GitLinks
P.S. If you decide to use Git as VCS for your project, consider adding entry
about it on http://git.or.cz/gitwiki/GitProjects wiki page.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git (at FreeNode)
next prev parent reply other threads:[~2006-07-05 19:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-04 0:56 Why's Git called Git ? Aaron Gray
2006-07-04 3:28 ` Linus Torvalds
2006-07-05 19:58 ` Aaron Gray
2006-07-05 19:33 ` Jakub Narebski [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-06 2:18 Aaron Gray
2006-07-07 18:40 ` Jakub Narebski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='e8h466$o4$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.