diff options
author | Junio C Hamano <junkio@cox.net> | 2005-06-03 12:11:07 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@ppc970.osdl.org> | 2005-06-12 20:40:19 -0700 |
commit | d327b89a224e6d8db37ad97be1f8c0a54e380a29 (patch) | |
tree | c1fd3ad296dc9956b1d09b675f779b98474edc52 | |
parent | 2210100ac00b8a46f1d94c044391bfa50b25afa4 (diff) | |
download | git-d327b89a224e6d8db37ad97be1f8c0a54e380a29.tar.gz git-d327b89a224e6d8db37ad97be1f8c0a54e380a29.tar.xz |
[PATCH] Tutorial update to adjust for -B fix
Now -B does not say silly "complete rewrite" anymore for small
files such as the one in the tutorial example.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-rw-r--r-- | Documentation/tutorial.txt | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/Documentation/tutorial.txt b/Documentation/tutorial.txt index 6faf7435a..a6eaba7b1 100644 --- a/Documentation/tutorial.txt +++ b/Documentation/tutorial.txt @@ -371,13 +371,6 @@ this point (you can continue to edit things and update the cache), you can just leave an empty message. Otherwise git-commit-script will commit the change for you. -(Btw, current versions of git will consider the change in question to be -so big that it's considered a whole new file, since the diff is actually -bigger than the file. So the helpful comments that git-commit-script -tells you for this example will say that you deleted and re-created the -file "a". For a less contrived example, these things are usually more -obvious). - You've now made your first real git commit. And if you're interested in looking at what git-commit-script really does, feel free to investigate: it's a few very simple shell scripts to generate the helpful (?) commit |