aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRobin Rosenberg <robin.rosenberg.lists@dewire.com>2007-02-04 17:16:39 +0100
committerJunio C Hamano <junkio@cox.net>2007-02-04 11:43:45 -0800
commit6e2e1cfb81a6a6de9fc074bd26bed8a45f73251f (patch)
tree012a1f8f59daea4ea8c18dcd5dc75f5240bedf00
parent1f7d1a53fed40608e76200f941e6689b53752747 (diff)
downloadgit-6e2e1cfb81a6a6de9fc074bd26bed8a45f73251f.tar.gz
git-6e2e1cfb81a6a6de9fc074bd26bed8a45f73251f.tar.xz
Why is it bad to rewind a branch that has already been pushed out?
Mention git-revert as an alternative to git-reset to revert changes. Signed-off-by: Robin Rosenberg <robin.rosenberg@dewire.com> Signed-off-by: Junio C Hamano <junkio@cox.net>
-rw-r--r--Documentation/tutorial.txt2
1 files changed, 2 insertions, 0 deletions
diff --git a/Documentation/tutorial.txt b/Documentation/tutorial.txt
index 5fc5be5a2..129c5c5f5 100644
--- a/Documentation/tutorial.txt
+++ b/Documentation/tutorial.txt
@@ -461,6 +461,8 @@ this branch. If this branch is the only branch containing those
commits, they will be lost. Also, don't use "git reset" on a
publicly-visible branch that other developers pull from, as it will
force needless merges on other developers to clean up the history.
+If you need to undo changes that you have pushed, use gitlink:git-revert[1]
+instead.
The git grep command can search for strings in any version of your
project, so