| commit | 1933f6ce4399262c0e4eac33e9d2893bf9824e7f | |
| author | Eric Sunshine <sunshine@sunshineco.com> | |
| Tue, 4 Aug 2020 00:55:34 +0000 (3 20:55 -0400) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Tue, 4 Aug 2020 04:32:25 +0000 (3 21:32 -0700) | ||
| tree | d0ff4a7070cdbf250cc51af951323fee6b175273 | treesnapshot (tar.gz zip) |
| parent | ff1ce500f72c1fd7b92d2d402235dbd28d8f7bb4 | commitdiff |
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 <sunshine@sunshineco.com>
Reviewed-by: Taylor Blau <me@ttaylorr.com>
Signed-off-by: Junio C Hamano <gitster@pobox.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>
Reviewed-by: Taylor Blau <me@ttaylorr.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| Documentation/git-worktree.txt | diffblobblamehistory |