git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Different behaviour of rebase -i

From
LCLeonardo Sobral Cunha <sobral@gmail.com>
Date
Oct 9, 2008, 19:04 UTC
Message-ID
<6beb92080810091204n6df4338fs3b182194a8d6454e@mail.gmail.com>
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: Caio Marcelo de Oliveira Filho
Message 1 of 4 in “Different behaviour of rebase -i”
  1. Leonardo Sobral CunhaOct 9, 2008
  2. Caio Marcelo de Oliveira FilhoOct 9, 2008
  3. Johannes SchindelinOct 10, 2008
  4. rebase -i: do not fail when there is no commit to cherry-pickJohannes Schindelin, Oct 10, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.