From: Eugene Sajine <euguess@gmail.com>
To: git@vger.kernel.org
Subject: [BUG] - git rebase -i performs rebase when it shouldn't?
Date: Fri, 9 Apr 2010 15:35:42 -0400 [thread overview]
Message-ID: <z2q76c5b8581004091235ucd9b2a52i223b3191b288c42a@mail.gmail.com> (raw)
Hi,
In case of this situation
A master
\
B next
\
C topic
$ git rebase --onto master topic
First, rewinding head to replay your work on top of it...
fatal: Not a range.
Nothing to do.
Which is OK.
When I fired up interactive rebase, it printed me “noop”, so I was
expecting it to do nothing and exited the vi, without deleting this
"noop". But it did performed some operation and I actually have commit
C lost, with topic pointing to the same commit as master.
$ git rebase -i --onto master topic
Successfully rebased and updated refs/heads/topic.
I believe this is wrong.
Thanks,
Eugene
next reply other threads:[~2010-04-09 19:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 19:35 Eugene Sajine [this message]
2010-04-10 4:26 ` [BUG] - git rebase -i performs rebase when it shouldn't? Jeff King
2010-04-10 4:39 ` Junio C Hamano
2010-04-10 4:47 ` Jeff King
2010-04-10 19:58 ` Johannes Sixt
2010-04-11 10:15 ` Jeff King
2010-04-11 17:54 ` Johannes Sixt
2010-04-12 1:01 ` Jeff King
2010-04-12 10:50 ` Michal Vitecek
2010-04-12 17:39 ` Johannes Sixt
2010-04-10 22:10 ` Eugene Sajine
2010-04-11 10:22 ` Jeff King
2010-04-11 14:06 ` Eugene Sajine
2010-04-12 14:09 ` Eugene Sajine
2010-04-12 15:13 ` Johannes Sixt
2010-04-12 15:28 ` Eugene Sajine
2010-04-12 15:47 ` Johannes Sixt
2010-04-13 16:30 ` Eugene Sajine
2010-04-14 6:08 ` Johannes Sixt
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=z2q76c5b8581004091235ucd9b2a52i223b3191b288c42a@mail.gmail.com \
--to=euguess@gmail.com \
--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).