-This document is a modified version originally known as "Distributed
-revision control with Mercurial" and originally authored by Bryan
-O’Sullivan. The original document was obtained from
+This document is a modified version of a document originally titled
+"Distributed revision control with Mercurial" and originally authored
+by Bryan O’Sullivan. The original document was obtained from
<http://hgbook.red-bean.com/>.
Copyright © 2006, 2007 Bryan O’Sullivan.
<http://hgbook.red-bean.com/>.
Copyright © 2006, 2007 Bryan O’Sullivan.
+The source of this modified version can be obtained via git:
+
+ git clone git://cworth.org/git/hgbook-git
+
+or
+
+ git clone http://cworth.org/git/hgbook-git
+
+and can be [browsed online](http://git.cworth.org/git/hgbook-git)
+
development environment necessary to work on improving the msysgit
port of git, and WinGit, a package for installing just git itself
without the development environment, (still in Alpha as of September
development environment necessary to work on improving the msysgit
port of git, and WinGit, a package for installing just git itself
without the development environment, (still in Alpha as of September
Another useful syntax is .. which can be used to specify a range of
commits. So "origin..master" specifies everything that has been
Another useful syntax is .. which can be used to specify a range of
commits. So "origin..master" specifies everything that has been
Another useful option is -n or --max-count which, unsurprisingly,
limits the maximum number of commits to be displayed.
Another useful option is -n or --max-count which, unsurprisingly,
limits the maximum number of commits to be displayed.
While the default information printed by “git log” is useful if you
already know what you’re looking for, you may need to see more details
While the default information printed by “git log” is useful if you
already know what you’re looking for, you may need to see more details