From: Johannes Sixt <j6t@kdbg.org>
To: Git Mailing List <git@vger.kernel.org>
Subject: Unexpected messages by git rebase -m
Date: Wed, 22 Apr 2009 21:55:54 +0200 [thread overview]
Message-ID: <200904222155.54422.j6t@kdbg.org> (raw)
I did the usual fix-up-the-second-commit procedure, this time with 'git
rebase -m'. The result is OK, but rebase writes something unexpected:
git init
echo a > x && git add x && git commit -m A
echo b > x && git add x && git commit -m B
echo c > x && git add x && git commit -m C
git checkout HEAD^
echo b1 > x && git add x && git commit --amend -m B1
Here we have this history:
A--B--C <- master
\
B1 <- detached HEAD
git rebase -m HEAD master
git rebase --skip # B is in conflict; we don't need it
git checkout master x # resolve another conflict
Now look what rebase has to say:
$ git rebase --continue
[detached HEAD 90c7916] C
1 files changed, 1 insertions(+), 1 deletions(-)
Committed: 0001 C
Already applied: 0002 C
All done.
Notice "Committed: 0001 C" followed by "Already applied: 0002 C". I'd expect
only "Committed: 0002 C". What's up?
-- Hannes
reply other threads:[~2009-04-22 19:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200904222155.54422.j6t@kdbg.org \
--to=j6t@kdbg.org \
--cc=git@vger.kernel.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 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).