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

git-rebase --merge gets stuck on --skip

From
MVMarius Vollmer <marius.vollmer@uni-dortmund.de>
Date
Aug 13, 2008, 01:51 UTC
Message-ID
<87y731adiy.fsf@uni-dortmund.de>
Hi,
I might have found a bug with "git-rebase --merge".

When skipping over more than one commit in a row, only the first skip has any effect. The second and subsequent skips do not change the state in .git/.dotest-merge.

This works fine with the regular git-rebase.
I use Debian's git-core 1:1.5.6.3-1.1.  I haven't tried newer versions.
How to reproduce:
  $ git clone http://zagadka.vm.bytemark.co.uk/git/project2.git
  $ cd project2/
  $ git checkout -b dev-1 origin/dev-1
  $ git rebase --merge master
  (fails with a conflict)
  $ cat .git/.dotest-merge/msgnum
  1
  $ git rebase --skip
  (fails with a different conflict)
  $ cat .git/.dotest-merge/msgnum
  1
  $ git rebase --skip
  (fails with the same conflict again)
  $ cat .git/.dotest-merge/msgnum
  1
  $ git rebase --skip
  $ cat .git/.dotest-merge/msgnum
  1
  $ git rebase --skip
  $ cat .git/.dotest-merge/msgnum
  1
  $ git rebase --skip
  $ cat .git/.dotest-merge/msgnum
  1
And so on ad infinitum...
In contrast, git-rebase without --merge eventually finishes:
  $ git clone http://zagadka.vm.bytemark.co.uk/git/project2.git
  $ cd project2/
  $ git checkout -b dev-1 origin/dev-1
  $ git rebase master
  (fails with a conflict)
  $ cat .dotest/next
  1
  $ git rebase --skip
  $ cat .dotest/next
  2
  $ git rebase --skip
  $ cat .dotest/next
  3
  $ git rebase --skip
  HEAD is now at 060b191 Master 2.
  Nothing to do.
Message 1 of 1 in “git-rebase --merge gets stuck on --skip”
  1. Marius VollmerAug 13, 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.