From: Robin Rosenberg Date: Sun, 4 Feb 2007 16:16:39 +0000 (+0100) Subject: Why is it bad to rewind a branch that has already been pushed out? X-Git-Tag: v1.5.0-rc4~50 X-Git-Url: https://git.tokkee.org/?a=commitdiff_plain;h=6e2e1cfb81a6a6de9fc074bd26bed8a45f73251f;p=git.git 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 Signed-off-by: Junio C Hamano --- 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