Skip to content

Commit

Permalink
Fix typos in the documentation.
Browse files Browse the repository at this point in the history
Signed-off-by: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
  • Loading branch information
Ralf Wildenhues authored and Junio C Hamano committed Nov 27, 2008
1 parent 5aa3bdd commit a0178ae
Show file tree
Hide file tree
Showing 4 changed files with 4 additions and 4 deletions.
2 changes: 1 addition & 1 deletion Documentation/RelNotes-1.6.0.4.txt
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ Fixes since v1.6.0.3
* 'git status' incorrectly reported a submodule directory as an untracked
directory.

* 'git svn' used deprecated 'git-foo' form of subcommand invocaition.
* 'git svn' used deprecated 'git-foo' form of subcommand invocation.

* 'git update-ref -d' to remove a reference did not honor --no-deref option.

Expand Down
2 changes: 1 addition & 1 deletion Documentation/git-commit.txt
Original file line number Diff line number Diff line change
Expand Up @@ -92,7 +92,7 @@ OPTIONS

-s::
--signoff::
Add Signed-off-by line by the commiter at the end of the commit
Add Signed-off-by line by the committer at the end of the commit
log message.

-n::
Expand Down
2 changes: 1 addition & 1 deletion Documentation/git-svn.txt
Original file line number Diff line number Diff line change
Expand Up @@ -109,7 +109,7 @@ COMMANDS

This works similarly to `svn update` or 'git-pull' except that
it preserves linear history with 'git-rebase' instead of
'git-merge' for ease of dcommiting with 'git-svn'.
'git-merge' for ease of dcommitting with 'git-svn'.

This accepts all options that 'git-svn fetch' and 'git-rebase'
accept. However, '--fetch-all' only fetches from the current
Expand Down
2 changes: 1 addition & 1 deletion Documentation/user-manual.txt
Original file line number Diff line number Diff line change
Expand Up @@ -536,7 +536,7 @@ $ git bisect skip
-------------------------------------------------

In this case, though, git may not eventually be able to tell the first
bad one between some first skipped commits and a latter bad commit.
bad one between some first skipped commits and a later bad commit.

There are also ways to automate the bisecting process if you have a
test script that can tell a good from a bad commit. See
Expand Down

0 comments on commit a0178ae

Please sign in to comment.