From: Junio C Hamano <junkio@cox.net>
To: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Cc: git@vger.kernel.org
Subject: Re: Why is it bad to rewind a branch that has already been pushed out?
Date: Sun, 04 Feb 2007 12:08:40 -0800 [thread overview]
Message-ID: <7vlkjdr8hj.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 200702041716.39999.robin.rosenberg.lists@dewire.com
Robin Rosenberg <robin.rosenberg.lists@dewire.com> writes:
> Mention git-revert as an alternative to git-reset to revert changes.
Thanks; that makes sense. Applied.
It is not a biggie but for future reference you might want to
check your KMail configuration to avoid the wrapped line below:
> 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
next prev parent reply other threads:[~2007-02-04 20:08 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
2007-02-04 20:08 ` Junio C Hamano [this message]
[not found] ` <20070205132150.123659@dial-up-mi-449.lombardiacom.it>
2007-02-05 13:27 ` [PATCH] Documentation: add KMail in SubmittingPatches 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=7vlkjdr8hj.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=robin.rosenberg.lists@dewire.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).