Skip to content

Commit 1933f6c

Browse files
sunshinecogitster
authored andcommitted
git-worktree.txt: make start of new sentence more obvious
When reading the rendered description of `add`, it's easy to trip over and miss the end of one sentence and the start of the next, making it seem as if they are part of the same statement, separated only by a dash: ... specific files such as HEAD, index, etc. - may also be specified as <commit-ish>; it is synonymous with... This can be particularly confusing since the thoughts expressed by the two sentences are unrelated. Reduce the likelihood of confusion by making it obvious that the two sentences are distinct. Signed-off-by: Eric Sunshine <[email protected]> Reviewed-by: Taylor Blau <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent ff1ce50 commit 1933f6c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

Documentation/git-worktree.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -48,8 +48,8 @@ add <path> [<commit-ish>]::
4848

4949
Create `<path>` and checkout `<commit-ish>` into it. The new working directory
5050
is linked to the current repository, sharing everything except working
51-
directory specific files such as `HEAD`, `index`, etc. `-` may also be
52-
specified as `<commit-ish>`; it is synonymous with `@{-1}`.
51+
directory specific files such as `HEAD`, `index`, etc. As a convenience,
52+
`<commit-ish>` may be a bare "`-`", which is synonymous with `@{-1}`.
5353
+
5454
If `<commit-ish>` is a branch name (call it `<branch>`) and is not found,
5555
and neither `-b` nor `-B` nor `--detach` are used, but there does

0 commit comments

Comments
 (0)