From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Why is it bad to rewind a branch that has already been pushed out?
Date: Sun, 4 Feb 2007 17:16:39 +0100 [thread overview]
Message-ID: <200702041716.39999.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <7v1wl7bv66.fsf@assigned-by-dhcp.cox.net>
Mention git-revert as an alternative to git-reset to revert changes.
Signed-off-by: Robin Rosenberg <robin.rosenberg@dewire.com>
---
diff --git a/Documentation/tutorial.txt b/Documentation/tutorial.txt
index 5fc5be5..129c5c5 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
next prev parent reply other threads:[~2007-02-04 16:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-03 6:40 Why is it bad to rewind a branch that has already been pushed out? Junio C Hamano
2007-02-03 10:40 ` Andy Parkins
2007-02-03 19:42 ` Junio C Hamano
2007-02-04 18:01 ` Andy Parkins
2007-02-03 13:20 ` Theodore Tso
2007-02-04 16:16 ` Robin Rosenberg [this message]
2007-02-04 20:08 ` Junio C Hamano
2007-02-05 13:27 ` [PATCH] Documentation: add KMail in SubmittingPatches Michael
2007-02-05 13:27 ` Michael
2007-02-06 3:07 ` Junio C Hamano
2007-02-06 13:45 ` Michael
2007-02-06 14:16 ` Jakub Narebski
2007-02-06 14:47 ` Andy Parkins
-- strict thread matches above, loose matches on Subject: below --
2007-02-03 8:42 Why is it bad to rewind a branch that has already been pushed out? linux
2007-02-03 9:04 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200702041716.39999.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.