diff options
| author | Nicolas Pitre <nico@cam.org> | 2006-12-14 23:15:44 -0500 |
|---|---|---|
| committer | Junio C Hamano <junkio@cox.net> | 2006-12-15 22:29:54 -0800 |
| commit | ebd124c6783da5e064963611ee17741cd173f6b5 (patch) | |
| tree | d3e5ba5b8a6ef190bc1144c841105a2de24425c9 /Documentation/core-tutorial.txt | |
| parent | 1510fea781cb0517eeba8c378964f7bc4f9577ab (diff) | |
| download | git-ebd124c6783da5e064963611ee17741cd173f6b5.tar.gz git-ebd124c6783da5e064963611ee17741cd173f6b5.tar.xz | |
make commit message a little more consistent and conforting
It is nicer to let the user know when a commit succeeded all the time,
not only the first time. Also the commit sha1 is much more useful than
the tree sha1 in this case.
This patch also introduces a -q switch to supress this message as well
as the summary of created/deleted files.
Signed-off-by: Nicolas Pitre <nico@cam.org>
Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'Documentation/core-tutorial.txt')
| -rw-r--r-- | Documentation/core-tutorial.txt | 14 |
1 files changed, 3 insertions, 11 deletions
diff --git a/Documentation/core-tutorial.txt b/Documentation/core-tutorial.txt index 47505aa20..1c311590c 100644 --- a/Documentation/core-tutorial.txt +++ b/Documentation/core-tutorial.txt @@ -336,17 +336,9 @@ $ commit=$(echo 'Initial commit' | git-commit-tree $tree) $ git-update-ref HEAD $commit ------------------------------------------------ -which will say: - ----------------- -Committing initial tree 8988da15d077d4829fc51d8544c097def6644dbb ----------------- - -just to warn you about the fact that it created a totally new commit -that is not related to anything else. Normally you do this only *once* -for a project ever, and all later commits will be parented on top of an -earlier commit, and you'll never see this "Committing initial tree" -message ever again. +In this case this creates a totally new commit that is not related to +anything else. Normally you do this only *once* for a project ever, and +all later commits will be parented on top of an earlier commit. Again, normally you'd never actually do this by hand. There is a helpful script called `git commit` that will do all of this for you. So |