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>

diff --git a/Documentation/tutorial.txt b/Documentation/tutorial.txt
index 5fc5be5a287c5ac9e12ac8111cb9434f3c5d3d03..129c5c5f5b8657175db7efed2c06078affd05ab6 100644 (file)
--- 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.
 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
 
 The git grep command can search for strings in any version of your
 project, so