Fix typos in the documentation.
Signed-off-by: Ralf Wildenhues <Ralf.Wildenhues@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
parent
5aa3bdd50d
commit
a0178ae2cf
@ -30,7 +30,7 @@ Fixes since v1.6.0.3
|
|||||||
* 'git status' incorrectly reported a submodule directory as an untracked
|
* 'git status' incorrectly reported a submodule directory as an untracked
|
||||||
directory.
|
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.
|
* 'git update-ref -d' to remove a reference did not honor --no-deref option.
|
||||||
|
|
||||||
|
@ -92,7 +92,7 @@ OPTIONS
|
|||||||
|
|
||||||
-s::
|
-s::
|
||||||
--signoff::
|
--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.
|
log message.
|
||||||
|
|
||||||
-n::
|
-n::
|
||||||
|
@ -109,7 +109,7 @@ COMMANDS
|
|||||||
|
|
||||||
This works similarly to `svn update` or 'git-pull' except that
|
This works similarly to `svn update` or 'git-pull' except that
|
||||||
it preserves linear history with 'git-rebase' instead of
|
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'
|
This accepts all options that 'git-svn fetch' and 'git-rebase'
|
||||||
accept. However, '--fetch-all' only fetches from the current
|
accept. However, '--fetch-all' only fetches from the current
|
||||||
|
@ -536,7 +536,7 @@ $ git bisect skip
|
|||||||
-------------------------------------------------
|
-------------------------------------------------
|
||||||
|
|
||||||
In this case, though, git may not eventually be able to tell the first
|
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
|
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
|
test script that can tell a good from a bad commit. See
|
||||||
|
Loading…
Reference in New Issue
Block a user