[PATCH 4/4] git-worktree.txt: make start of new sentence more obvious
- From
Eric Sunshine <sunshine@sunshineco.com>
- Date
- Aug 3, 2020, 05:36 UTC
- Message-ID
- <20200803053612.50095-5-sunshine@sunshineco.com>
- In-Reply-To
- <20200803053612.50095-1-sunshine@sunshineco.com>
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 <sunshine@sunshineco.com> --- Documentation/git-worktree.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-worktree.txt b/Documentation/git-worktree.txt index 49422454d1..260bfe9105 100644 --- a/Documentation/git-worktree.txt +++ b/Documentation/git-worktree.txt @@ -48,8 +48,8 @@ add <path> [<commit-ish>]:: Create `<path>` and checkout `<commit-ish>` into it. The new working directory is linked to the current repository, sharing everything except working -directory specific files such as HEAD, index, etc. `-` may also be -specified as `<commit-ish>`; it is synonymous with `@{-1}`. +directory specific files such as HEAD, index, etc. As a convenience, +`<commit-ish>` may be a bare "`-`", which is synonymous with `@{-1}`. + If `<commit-ish>` is a branch name (call it `<branch>`) and is not found, and neither `-b` nor `-B` nor `--detach` are used, but there does
-- 2.28.0.236.gb10cc79966