summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 2210100)
raw | patch | inline | side by side (parent: 2210100)
author | Junio C Hamano <junkio@cox.net> | |
Fri, 3 Jun 2005 19:11:07 +0000 (12:11 -0700) | ||
committer | Linus Torvalds <torvalds@ppc970.osdl.org> | |
Mon, 13 Jun 2005 03:40:19 +0000 (20:40 -0700) |
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>
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>
Documentation/tutorial.txt | patch | blob | history |
index 6faf7435a821d8d54f2e0653f1bb8726af4132cd..a6eaba7b105f656c6293bbbdb19bbd39fc176228 100644 (file)
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