From: Junio C Hamano <gitster@pobox.com>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: "Git Mailinglist" <git@vger.kernel.org>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Eric Wong" <normalperson@yhbt.net>,
"Shawn O. Pear,
Sverre Rabbelier
<srabbelier@gmail.com>"@b-sasl-quonix.sasl.smtp.pobox.com
Subject: Re: [RFC PATCH] Teach rebase to rebase even if upstream is up to date with -f
Date: Thu, 12 Feb 2009 13:34:59 -0800 [thread overview]
Message-ID: <7vbpt7jq4c.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1234468061-29923-1-git-send-email-srabbelier@gmail.com> (Sverre Rabbelier's message of "Thu, 12 Feb 2009 20:47:41 +0100")
Sverre Rabbelier <srabbelier@gmail.com> writes:
> Say I have a bunch of new commits ready to submit to origin, but I want to fix
> some whitespace damage, I could do something like this:
>
> $ git checkout master
> $ git branch -b rebase-me
> $ git reset --hard origin/master
> $ git commit --allow-empty "force rebase"
> $ git checkout rebase-me
> $ git rebase --whitespace=fix master
> $ git rebase -i master # kick out the 'force rebase' commit
> $ git checkout master
> $ git reset --hard rebase-me
> $ git branch -d rebase-me
For that, I would prefer to see:
git format-patch --stdout origin >my.mbox
git fetch origin
git checkout origin ;# yes, detach
git am --whitespace=fix my.mbox
make test
git format-patch -o to-send-out origin
git send-email ..options.. to-send-out
for two reasons.
It fixes whitespace breakages, but more importantly, the procedure makes
sure that what you will be sending out will apply cleanly to the origin
that may have progressed since you last looked at it.
next prev parent reply other threads:[~2009-02-12 21:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 19:47 [RFC PATCH] Teach rebase to rebase even if upstream is up to date with -f Sverre Rabbelier
2009-02-12 20:28 ` Johannes Schindelin
2009-02-12 20:30 ` Sverre Rabbelier
2009-02-12 20:37 ` Johannes Schindelin
2009-02-12 20:44 ` Sverre Rabbelier
2009-02-12 21:34 ` Junio C Hamano [this message]
2009-02-12 21:57 ` Sverre Rabbelier
2009-02-12 23:22 ` Junio C Hamano
2009-02-12 23:24 ` Sverre Rabbelier
2009-02-13 1:32 ` Junio C Hamano
2009-02-13 6:02 ` Sverre Rabbelier
2009-02-13 6:22 ` Junio C Hamano
2009-02-13 6:51 ` Sverre Rabbelier
2009-02-13 7:15 ` 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=7vbpt7jq4c.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc="Shawn O. Pear, Sverre Rabbelier <srabbelier@gmail.com>"@b-sasl-quonix.sasl.smtp.pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
--cc=srabbelier@gmail.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 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.