mirror of
https://github.com/git/git.git
synced 2024-05-09 13:46:08 +02:00
Fix typos in documentation
Signed-off-by: Eisuke Kawashima <e.kawaschima+git@gmail.com>
This commit is contained in:
parent
4d53e91c6b
commit
9056fa3de8
|
@ -50,7 +50,7 @@ mergetool.hideResolved::
|
|||
possible and write the 'MERGED' file containing conflict markers around
|
||||
any conflicts that it cannot resolve; 'LOCAL' and 'REMOTE' normally
|
||||
represent the versions of the file from before Git's conflict
|
||||
resolution. This flag causes 'LOCAL' and 'REMOTE' to be overwriten so
|
||||
resolution. This flag causes 'LOCAL' and 'REMOTE' to be overwritten so
|
||||
that only the unresolved conflicts are presented to the merge tool. Can
|
||||
be configured per-tool via the `mergetool.<tool>.hideResolved`
|
||||
configuration variable. Defaults to `false`.
|
||||
|
|
|
@ -119,7 +119,7 @@ for example:
|
|||
myuser:$5$.NqmNH1vwfzGpV8B$znZIcumu1tNLATgV2l6e1/mY8RzhUDHMOaVOeL1cxV3
|
||||
------
|
||||
You can use the 'htpasswd' facility that comes with Apache to make these
|
||||
files, but only with the -d option (or -B if your system suports it).
|
||||
files, but only with the -d option (or -B if your system supports it).
|
||||
|
||||
Preferably use the system specific utility that manages password hash
|
||||
creation in your platform (e.g. mkpasswd in Linux, encrypt in OpenBSD or
|
||||
|
|
|
@ -242,7 +242,7 @@ populated with placeholder text.
|
|||
or "--reroll-count=4rev2" are allowed), but the downside of
|
||||
using such a reroll-count is that the range-diff/interdiff
|
||||
with the previous version does not state exactly which
|
||||
version the new interation is compared against.
|
||||
version the new iteration is compared against.
|
||||
|
||||
--to=<email>::
|
||||
Add a `To:` header to the email headers. This is in addition
|
||||
|
|
|
@ -33,7 +33,7 @@ from warnings to errors (so e.g. a missing "tagger" line is an error).
|
|||
|
||||
Extra headers in the object are also an error under mktag, but ignored
|
||||
by linkgit:git-fsck[1]. This extra check can be turned off by setting
|
||||
the appropriate `fsck.<msg-id>` varible:
|
||||
the appropriate `fsck.<msg-id>` variable:
|
||||
|
||||
git -c fsck.extraHeaderEntry=ignore mktag <my-tag-with-headers
|
||||
|
||||
|
|
|
@ -40,7 +40,7 @@ Values 1-4 satisfy the requirements of parse_commit_gently().
|
|||
|
||||
There are two definitions of generation number:
|
||||
1. Corrected committer dates (generation number v2)
|
||||
2. Topological levels (generation nummber v1)
|
||||
2. Topological levels (generation number v1)
|
||||
|
||||
Define "corrected committer date" of a commit recursively as follows:
|
||||
|
||||
|
@ -48,7 +48,7 @@ Define "corrected committer date" of a commit recursively as follows:
|
|||
equal to its committer date.
|
||||
|
||||
* A commit with at least one parent has corrected committer date equal to
|
||||
the maximum of its commiter date and one more than the largest corrected
|
||||
the maximum of its committer date and one more than the largest corrected
|
||||
committer date among its parents.
|
||||
|
||||
* As a special case, a root commit with timestamp zero has corrected commit
|
||||
|
|
Loading…
Reference in New Issue