summaryrefslogtreecommitdiff
path: root/Documentation/git-tag.txt
diff options
context:
space:
mode:
authorRalf Wildenhues <Ralf.Wildenhues@gmx.de>2007-10-09 21:00:03 (GMT)
committerShawn O. Pearce <spearce@spearce.org>2007-10-16 02:11:02 (GMT)
commit06ada1529ce46e84aaef4e5608c1101c1c7ec73f (patch)
tree7a57504018332d6857c17f474a27681f1c91b4a6 /Documentation/git-tag.txt
parent2ef8ac1b2a2d310642b8ae4dbec4b8173b4b1213 (diff)
downloadgit-06ada1529ce46e84aaef4e5608c1101c1c7ec73f.zip
git-06ada1529ce46e84aaef4e5608c1101c1c7ec73f.tar.gz
git-06ada1529ce46e84aaef4e5608c1101c1c7ec73f.tar.bz2
Fix some typos, punctuation, missing words, minor markup.
Signed-off-by: Lars Hjemli <hjemli@gmail.com> Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Diffstat (limited to 'Documentation/git-tag.txt')
-rw-r--r--Documentation/git-tag.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/git-tag.txt b/Documentation/git-tag.txt
index 990ae4f..22a23bf 100644
--- a/Documentation/git-tag.txt
+++ b/Documentation/git-tag.txt
@@ -112,7 +112,7 @@ 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
+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
one.