Documentation: fix typos in man pages
Signed-off-by: Øystein Walle <oystwa@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
parent
3330a2c4f6
commit
5fe8f49b6d
@ -213,7 +213,7 @@ objects from the source repository into a pack in the cloned repository.
|
|||||||
--separate-git-dir=<git dir>::
|
--separate-git-dir=<git dir>::
|
||||||
Instead of placing the cloned repository where it is supposed
|
Instead of placing the cloned repository where it is supposed
|
||||||
to be, place the cloned repository at the specified directory,
|
to be, place the cloned repository at the specified directory,
|
||||||
then make a filesytem-agnostic Git symbolic link to there.
|
then make a filesystem-agnostic Git symbolic link to there.
|
||||||
The result is Git repository can be separated from working
|
The result is Git repository can be separated from working
|
||||||
tree.
|
tree.
|
||||||
|
|
||||||
|
@ -44,7 +44,7 @@ two blob objects, or changes between two files on disk.
|
|||||||
commit relative to the named <commit>. Typically you
|
commit relative to the named <commit>. Typically you
|
||||||
would want comparison with the latest commit, so if you
|
would want comparison with the latest commit, so if you
|
||||||
do not give <commit>, it defaults to HEAD.
|
do not give <commit>, it defaults to HEAD.
|
||||||
If HEAD does not exist (e.g. unborned branches) and
|
If HEAD does not exist (e.g. unborn branches) and
|
||||||
<commit> is not given, it shows all staged changes.
|
<commit> is not given, it shows all staged changes.
|
||||||
--staged is a synonym of --cached.
|
--staged is a synonym of --cached.
|
||||||
|
|
||||||
|
@ -28,7 +28,7 @@ arguments. Here are the rules:
|
|||||||
they can be disambiguated by placing `--` between them.
|
they can be disambiguated by placing `--` between them.
|
||||||
E.g. `git diff -- HEAD` is, "I have a file called HEAD in my work
|
E.g. `git diff -- HEAD` is, "I have a file called HEAD in my work
|
||||||
tree. Please show changes between the version I staged in the index
|
tree. Please show changes between the version I staged in the index
|
||||||
and what I have in the work tree for that file". not "show difference
|
and what I have in the work tree for that file", not "show difference
|
||||||
between the HEAD commit and the work tree as a whole". You can say
|
between the HEAD commit and the work tree as a whole". You can say
|
||||||
`git diff HEAD --` to ask for the latter.
|
`git diff HEAD --` to ask for the latter.
|
||||||
|
|
||||||
|
@ -251,7 +251,7 @@ three parameters:
|
|||||||
|
|
||||||
- the name of the ref being updated,
|
- the name of the ref being updated,
|
||||||
- the old object name stored in the ref,
|
- the old object name stored in the ref,
|
||||||
- and the new objectname to be stored in the ref.
|
- and the new object name to be stored in the ref.
|
||||||
|
|
||||||
A zero exit from the update hook allows the ref to be updated.
|
A zero exit from the update hook allows the ref to be updated.
|
||||||
Exiting with a non-zero status prevents 'git-receive-pack'
|
Exiting with a non-zero status prevents 'git-receive-pack'
|
||||||
|
@ -630,13 +630,13 @@ need to set this element to empty list i.e. `[]`.
|
|||||||
|
|
||||||
override::
|
override::
|
||||||
If this field has a true value then the given feature is
|
If this field has a true value then the given feature is
|
||||||
overriddable, which means that it can be configured
|
overridable, which means that it can be configured
|
||||||
(or enabled/disabled) on a per-repository basis.
|
(or enabled/disabled) on a per-repository basis.
|
||||||
+
|
+
|
||||||
Usually given "<feature>" is configurable via the `gitweb.<feature>`
|
Usually given "<feature>" is configurable via the `gitweb.<feature>`
|
||||||
config variable in the per-repository Git configuration file.
|
config variable in the per-repository Git configuration file.
|
||||||
+
|
+
|
||||||
*Note* that no feature is overriddable by default.
|
*Note* that no feature is overridable by default.
|
||||||
|
|
||||||
sub::
|
sub::
|
||||||
Internal detail of implementation. What is important is that
|
Internal detail of implementation. What is important is that
|
||||||
|
@ -3795,7 +3795,7 @@ like so:
|
|||||||
$ git update-index filename
|
$ git update-index filename
|
||||||
-------------------------------------------------
|
-------------------------------------------------
|
||||||
|
|
||||||
but to avoid common mistakes with filename globbing etc, the command
|
but to avoid common mistakes with filename globbing etc., the command
|
||||||
will not normally add totally new entries or remove old entries,
|
will not normally add totally new entries or remove old entries,
|
||||||
i.e. it will normally just update existing cache entries.
|
i.e. it will normally just update existing cache entries.
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user