From: Stephen Haberman <stephen@exigencecorp.com>
To: Johannes Sixt <j6t@kdbg.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] Fix t3411.3 to actually rebase something
Date: Fri, 18 May 2012 10:15:32 -0500 [thread overview]
Message-ID: <20120518101532.0c0c9dcf@sh9> (raw)
In-Reply-To: <4FB65345.3090201@kdbg.org>
> The test intends to rebase a branchy history onto a later commit, but
> it forgot to reset HEAD back to an earlier commit before it set up
> the side branches. In the end, every "rebased" commit was only a
> fast-forward and the 'rebase -p' did not change the commit graph at
> all. Insert the missing checkout that moves to an earlier commit.
Makes sense to me. Thanks, Johannes.
- Stephen
prev parent reply other threads:[~2012-05-18 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 13:48 [PATCH] Fix t3411.3 to actually rebase something Johannes Sixt
2012-05-18 15:15 ` Stephen Haberman [this message]
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=20120518101532.0c0c9dcf@sh9 \
--to=stephen@exigencecorp.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
/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.