summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 6ed6405)
raw | patch | inline | side by side (parent: 6ed6405)
author | Junio C Hamano <junkio@cox.net> | |
Sun, 20 Nov 2005 03:21:11 +0000 (19:21 -0800) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Sun, 20 Nov 2005 03:21:11 +0000 (19:21 -0800) |
git-commit -v flag has been the default for quite some time, so
do not mention it. Also a typofix.
Signed-off-by: Junio C Hamano <junkio@cox.net>
do not mention it. Also a typofix.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Documentation/howto/rebase-from-internal-branch.txt | patch | blob | history |
diff --git a/Documentation/howto/rebase-from-internal-branch.txt b/Documentation/howto/rebase-from-internal-branch.txt
index b2c021d91723de411163a8379a017c594362beda..c2d4a91c7cf0a631ffd3caadea8a6aa25aa4a24c 100644 (file)
$ git checkout master
$ cd Documentation; ed git.txt ...
$ cd ..; git add Documentation/*.txt
- $ git commit -s -v
-
-NOTE. The -v flag to commit is a handy way to make sure that
-your additions are not introducing bogusly formatted lines.
+ $ git commit -s
After the commit, the ancestry graph would look like this:
Let's go back to the earlier picture, with different labels.
You, as an individual developer, cloned upstream repository and
-amde a couple of commits on top of it.
+made a couple of commits on top of it.
*your "master" head
upstream --> #1 --> #2 --> #3