Skip to content

Commit 6e2e1cf

Browse files
Robin RosenbergJunio C Hamano
authored andcommitted
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>
1 parent 1f7d1a5 commit 6e2e1cf

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

Documentation/tutorial.txt

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -461,6 +461,8 @@ this branch. If this branch is the only branch containing those
461461
commits, they will be lost. Also, don't use "git reset" on a
462462
publicly-visible branch that other developers pull from, as it will
463463
force needless merges on other developers to clean up the history.
464+
If you need to undo changes that you have pushed, use gitlink:git-revert[1]
465+
instead.
464466

465467
The git grep command can search for strings in any version of your
466468
project, so

0 commit comments

Comments
 (0)