diff options
author | Jonathan Nieder <jrnieder@uchicago.edu> | 2008-07-01 02:17:07 +0400 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2008-07-02 04:20:09 +0400 |
commit | 46e56e81b3bc91af7071809fbda8dcdec22c4cb1 (patch) | |
tree | 6ac4f9e3daf65f770dd9c767b441367d2b9b0d37 /Documentation/git-tag.txt | |
parent | 963a653fa635c6b07ed399b2fafca2a4d7866a21 (diff) |
Documentation: prepare to be consistent about "git-" versus "git "
With the dashed forms of git commands not in $(bindir), we have
to change many instances of "git-command" to "git command". Also,
for consistency it is at times appropriate to make the opposite
change. In some cases, the change is not so simple as changing one
character.
This patch gets rid of some of those cases by rewrapping lines.
Signed-off-by: Jonathan Nieder <jrnieder@uchicago.edu>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/git-tag.txt')
-rw-r--r-- | Documentation/git-tag.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/git-tag.txt b/Documentation/git-tag.txt index 8f40f4bf0d..0c41711115 100644 --- a/Documentation/git-tag.txt +++ b/Documentation/git-tag.txt @@ -122,8 +122,8 @@ 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 "git -pull" on your tree shouldn't just make them overwrite the old +users back. So if somebody already got the old tag, doing a +"git pull" on your tree shouldn't just make them overwrite the old one. If somebody got a release tag from you, you cannot just change |