From: "Leonardo Sobral Cunha" <sobral@gmail.com>
To: git@vger.kernel.org
Subject: Different behaviour of rebase -i
Date: Thu, 9 Oct 2008 16:04:32 -0300 [thread overview]
Message-ID: <6beb92080810091204n6df4338fs3b182194a8d6454e@mail.gmail.com> (raw)
hi,
While doing a git rebase with my upstream branch ahead of my local
branch, first git rewinds my local branch to point to the upstream and
then prints "Nothing to do". As expected, my local branch ends
pointing to the upstream head.
But when I use the same command with the same branches using git
rebase -i, nothing happens and my local branch does not point to
upstream (the behaviour is different).
Is this different behaviour of rebase -i expected or is this a bug?
This is still happening in git version 1.6.0.2.443.g52e83
br,
--
// leo
next reply other threads:[~2008-10-09 19:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 19:04 Leonardo Sobral Cunha [this message]
2008-10-09 23:25 ` Different behaviour of rebase -i Caio Marcelo de Oliveira Filho
2008-10-10 11:40 ` Johannes Schindelin
2008-10-10 11:42 ` [PATCH] rebase -i: do not fail when there is no commit to cherry-pick Johannes Schindelin
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=6beb92080810091204n6df4338fs3b182194a8d6454e@mail.gmail.com \
--to=sobral@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).