Below there is email I want to send to Shlomi Fish to have him include GIT in "Better SCM Initiative : Comparison page".
Please check it and send comments and corrections. TIA.
-- >8 --
I have noticed that your SCM comparison at "Better SCM Initiative" website
http://better-scm.berlios.de/comparison/comparison.html
misses GIT, version control system which is used to manage Linux kernel.
GIT was created by Linus Torvalds in response to the change of BitKeeper licensing, as a tool to manage Linux kernel sources. It is based on three years of Linus experience with BitKeeper, and inspired by Monotone architecture. It was designed for Linux kernel, and is used by various projects, including X.Org, various Freedesktop projects, WINE, OLPC (One Laptop Per Child), Samba.
<blurb src="http://git-scm.org"> Git is a popular version control system designed to handle very large projects with speed and efficiency; it is used mainly for various open source projects, most notably the Linux kernel.
Git falls in the category of distributed source code management tools, similar to e.g. GNU Arch or Monotone (or BitKeeper in the proprietary world). Every Git working directory is a full-fledged repository with full revision tracking capabilities, not dependent on network access or a central server.
Git is an Open Source project covered by the GNU General Public License v2. It was originally written by Linus Torvalds and is currently maintained by Junio C Hamano. </blurb>
Below there is patch to the sources for the site.
BTW. when asking about updating GIT info for comparison, please CC git mailing list, git@vger.kernel.org
Index: src/comparison/scm-comparison.xml
===================================================================
--- src/comparison/scm-comparison.xml (revision 290)
+++ src/comparison/scm-comparison.xml (working copy)
@@ -38,6 +38,9 @@ <implementations>
<impl id="darcs">
<name>Darcs</name>
</impl>
+ <impl id="git">
+ <name>Git</name>
+ </impl>
<impl id="mercurial">
<name>Mercurial</name>
</impl>
@@ -106,6 +109,7 @@ <title>Atomic Commits</title>
<s id="svk">Commits are atomic.</s>
<s id="aegis">Commits are atomic.</s>
<s id="bitkeeper">Yes (but need to verify)</s>
+ <s id="git">Yes.</s>
<s id="mercurial">Yes.</s>
<s id="monotone">Yes.</s>
<s id="opencm">Yes. Commits are atomic.</s>
@@ -142,6 +146,13 @@ <title>Files and Directories Moves or Renames</title>
<s id="darcs">Yes. Renames are supported.</s>
<s id="bitkeeper">Yes. Renames are supported.</s>
<s id="aegis">Yes. Renames are supported.</s>
+ <s id="git">
+ Yes (or no depending on interpretation). Git detects
+ renames based on content regardless of whether the
+ committer indicated the fact.
+ You can follow history of file across renames using
+ 'git log -M --follow'.
+ </s>
<s id="mercurial">Yes. Renames are supported.</s>
<s id="monotone">Yes. Renames are supported.</s>
<s id="opencm">Yes. Renames are supported</s>
@@ -214,6 +225,13 @@ <title>File and Directories Copies</title>
Yes. Copies are supported.
</s>
<s id="aegis">No. Copies are not supported.</s>
+ <s id="git">
+ Yes (or no depending on interpretation). Git detects
+ copies (when requested) based on content regardless
+ of whether the committer indicated the fact.
+ You can follow history of file across copies using
+ 'git log -C -C --follow'.
+ </s>
<s id="mercurial">Yes. Copies are supported</s>
<s id="monotone">Yes. Copies are supported</s>
<s id="opencm">No. Copies are not supported.</s>
@@ -267,6 +285,7 @@ <title>Remote Repository Replication</title>
<s id="darcs">Yes.</s>
<s id="bitkeeper">Yes.</s>
<s id="aegis">Yes.</s>
+ <s id="git">Yes.</s>
<s id="mercurial">Yes.</s>
<s id="monotone">Yes.</s>
<s id="opencm">No.</s>
@@ -313,6 +332,7 @@ <title>Propagating Changes to Parent Repositories</title>
<s id="darcs">Yes.</s>
<s id="bitkeeper">Yes.</s>
<s id="aegis">Yes.</s>
+ <s id="git">Yes.</s>
<s id="mercurial">Yes.</s>
<s id="monotone">Yes.</s>
<s id="opencm">No.</s>
@@ -373,6 +393,10 @@ <title>Repository Permissions</title>
<s id="svk">
Same as subversion.
</s>
+ <s id="git">
+ Partial (?). It is possible to lock down repository
+ (access to branches and tags) using hooks.
+ </s>
<s id="mercurial">
Yes. It is possible to lock down repositories,
subdirectories, or files using hooks.
@@ -455,6 +479,13 @@ <title>Changesets' Support</title>
<s id="darcs">
Yes. Changesets are supported.
</s>
+ <s id="git">
+ Yes. Changesets are supported.<br />
+ Actually Git is snapshot based which means Git records
+ the full state in every commit. This means that any two
+ commits can be compared directly very quickly, although the
+ repository is typically browsed as a series of changesets.
+ </s>
<s id="mercurial">
Yes. Changesets are supported.
</s>
@@ -509,6 +540,11 @@ <title>Tracking Line-wise File History</title>
<s id="arch">Not in the command line client, but ViewARCH,
a web-interface for Arch, has it.</s>
<s id="darcs">Yes. (darcs annotate)</s>
+ <s id="git">
+ Yes. (git blame, git gui blame).
+ It can also detect the origin of copied and moved source
+ lines, and can ignore whitespace changes.
+ </s>
<s id="mercurial">Yes. (hg annotate)</s>
<s id="monotone">Yes, as of version 0.19.</s>
<s id="aegis">Yes. aeannotate</s>
@@ -570,6 +606,11 @@ <title>Ability to Work only on One Directory...</title>
whole.
</s>
<s id="aegis">No. All changes are made repository-wide.</s>
+ <s id="git">
+ No. All changes are made repository-wide. However
+ it is possible to commit only selected changes in the
+ working tree rather than everything. You can also
+ use submodules (subproject) support.</s>
<s id="mercurial">
It is possible to commit changes only in a subset of the
tree. There are plans for partial checkouts.
@@ -636,6 +677,10 @@ <title>Tracking Uncommited Changes</title>
Yes, using "darcs whatsnew".
</s>
<s id="aegis">Yes. Using aediff</s>
+ <s id="git">
+ Yes, of course. Using git diff.
+ Note that git uses staging area for commits (index).
+ </s>
<s id="mercurial">Yes. Using hg diff.</s>
<s id="monotone">Yes. In a similar fashion to CVS.</s>
<s id="opencm">Yes. Using cm diff</s>
@@ -681,6 +726,11 @@ <title>Per-File Commit Messages</title>
<s id="darcs">
No.
</s>
+ <s id="git">
+ No. The message applies to the commit as a whole.
+ But you can tag (with description) given contents
+ of a file (blob).
+ </s>
<s id="mercurial">
No.
</s>
@@ -782,6 +832,15 @@ <title>Documentation</title>
and the client contains a help tool that offers
an integrated help system.
</s>
+ <s id="git">
+ Good. There's Git User's Manual, manpages, some
+ technical documentation and some howtos. All
+ documentation is also available
+ <a href="http://www.kernel.org/pub/software/scm/git/docs">online</a>
+ in HTML format; there is additional information (including
+ beginnings of FAQ) on a
+ <a href="http://git-scm.org/gitwiki">git wiki</a>.
+ </s>
<s id="mercurial">
Very good. There's an overview and tutorial on the
web site, and integrated help for every command.
@@ -894,6 +953,16 @@ <title>Ease of Deployment</title>
to install the subversion perl bindings and a few modules
from CPAN.
</s>
+ <s id="git">
+ Very good. Install from RPM or deb on Linux; use
+ msysGit or Cygwin install on Windows. Git requires
+ zlib; also POSIX shell and utilities and Perl for some
+ commands.
+ Installing from sources is easy: Makefile has ready
+ configuration for many OS, you can also use autoconf
+ to generate Makefile configuration. Compiling docs
+ requires asciidoc toolchain, but you can use prebuild.
+ </s>
<s id="mercurial">
Excellent. Binary packages are available for all
popular platforms. Building from source requires
@@ -1006,6 +1075,13 @@ <title>Command Set</title>
but since the model is different most commands are
unique.
</s>
+ <s id="git">
+ Tries to follow CVS conventions, but deviates where there
+ is a different design (following BitKeeper for DVCS).
+ Large command set (~140) is divided into plumbing commands
+ (low lewel, to be used in scripts) and porcelain (high level).
+ It is easy to add new commands as scripts, or as git aliases.
+ </s>
<s id="mercurial">
Tries to follow CVS conventions, but deviates where there
is a different design.
@@ -1106,6 +1182,13 @@ <title>Networking Support</title>
There exists some HTTP-functionality, but it is quite
limited.
</s>
+ <s id="git">
+ Excellent. Uses HTTPS (with WebDAV) or ssh for push
+ (to publish changes to server) and HTTP, FTP, ssh or custom
+ "git" protocol for fetch (read from server). There is also
+ git-bundle for offline transport, and tools to exchange
+ (create and apply) patches via email.
+ </s>
<s id="mercurial">
Excellent. Uses HTTP or ssh. Remote access also
works safely without locks over read-only network
@@ -1203,6 +1286,11 @@ <title>Portability</title>
Very good. Supports many UNIXes, Mac OS X, and Windows,
and is written in a portable language.
</s>
+ <s id="git">
+ Good to very good. Portable across all POSIX systems.
+ There exists Win32 binary using MinGW (msysGit),
+ or you can use binary provided by Cygwin.
+ </s>
<s id="mercurial">
Excellent. Runs on all platforms supported by
Python. Repositories are portable across CPU
@@ -1300,6 +1388,10 @@ <title>Web Interface</title>
is included in the distribution.
</s>
<s id="aegis">Yes.</s>
+ <s id="git">
+ Yes, gitweb is included in git since version 1.4.0.
+ Other web interfaces exists: cgit, wit, git-php
+ </s>
<s id="mercurial">Yes. The web interface is a bundled component.</s>
<s id="monotone">No.</s>
<s id="opencm">No.</s>
@@ -1373,6 +1464,12 @@ <title>Availability of Graphical User-Interfaces.</title>
<s id="aegis">
There is tkaegis.
</s>
+ <s id="git">
+ There is history viewer 'gitk' and commit tool 'git-gui';
+ both in Tcl/Tk. There also exists a number of third-party
+ GUIs, including: qgit (Qt), GitView (GTK+), Giggle (GTK+),
+ tig (ncurses).
+ </s>
<s id="mercurial">
History viewing available with hgit extension;
check-in extension (hgct) makes committing easier.
@@ -1453,6 +1550,7 @@ <title>License</title>
GNU GPL (open-source)
</s>
<s id="svk">Perl License. (open source)</s>
+ <s id="git">GNU GPL v2 (open source)</s>
<s id="mercurial">GNU GPL (open source)</s>
<s id="monotone">GNU GPL (open source)</s>
<s id="opencm">
Jakub Narebski
