aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJunio C Hamano <junkio@cox.net>2005-11-19 19:21:11 -0800
committerJunio C Hamano <junkio@cox.net>2005-11-19 19:21:11 -0800
commit22a06b3c474d256e945dbc0d2a830c3f467288b5 (patch)
treefbe4060a1b8ba894be5767ffc27402f94f356882
parent6ed64058e1241f9939c4abf5d6a9eaed6a2cc795 (diff)
downloadgit-22a06b3c474d256e945dbc0d2a830c3f467288b5.tar.gz
git-22a06b3c474d256e945dbc0d2a830c3f467288b5.tar.xz
Documentation: rebase-from-internal minor updates.
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>
-rw-r--r--Documentation/howto/rebase-from-internal-branch.txt7
1 files changed, 2 insertions, 5 deletions
diff --git a/Documentation/howto/rebase-from-internal-branch.txt b/Documentation/howto/rebase-from-internal-branch.txt
index b2c021d91..c2d4a91c7 100644
--- a/Documentation/howto/rebase-from-internal-branch.txt
+++ b/Documentation/howto/rebase-from-internal-branch.txt
@@ -40,10 +40,7 @@ So I started from master, made a bunch of edits, and committed:
$ 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:
@@ -98,7 +95,7 @@ to do cherrypicking using only the core GIT tools.
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