diff options
author | Jean-Noël Avila <jn.avila@free.fr> | 2019-01-22 21:16:35 +0100 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2019-01-23 11:37:29 -0800 |
commit | ba170517be039a04b1914ebe9b492d4139c707df (patch) | |
tree | dcb778077f34381cddcb9569dab4a3eed34596e8 /Documentation/git-tag.txt | |
parent | 0d0ac3826a3bbb9247e39e12623bbcfdd722f24c (diff) | |
download | git-ba170517be039a04b1914ebe9b492d4139c707df.tar.gz |
doc: tidy asciidoc style
This mainly refers to enforcing indentation on additional lines of
items of lists.
Signed-off-by: Jean-Noël Avila <jn.avila@free.fr>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/git-tag.txt')
-rw-r--r-- | Documentation/git-tag.txt | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/Documentation/git-tag.txt b/Documentation/git-tag.txt index f2d644e3af..a74e7b926d 100644 --- a/Documentation/git-tag.txt +++ b/Documentation/git-tag.txt @@ -237,16 +237,16 @@ your repository directly), then others will have already seen the old tag. In that case you can do one of two things: . The sane thing. -Just admit you screwed up, and use a different name. Others have -already seen one tag-name, and if you keep the same name, you -may be in the situation that two people both have "version X", -but they actually have 'different' "X"'s. So just call it "X.1" -and be done with it. + Just admit you screwed up, and use a different name. Others have + already seen one tag-name, and if you keep the same name, you + may be in the situation that two people both have "version X", + but they actually have 'different' "X"'s. So just call it "X.1" + and be done with it. . The insane thing. -You really want to call the new version "X" too, 'even though' -others have already seen the old one. So just use 'git tag -f' -again, as if you hadn't already published the old one. + You really want to call the new version "X" too, 'even though' + others have already seen the old one. So just use 'git tag -f' + again, as if you hadn't already published the old one. However, Git does *not* (and it should not) change tags behind users back. So if somebody already got the old tag, doing a |