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

Re: Small rerere in rebase regression

From
Johannes Sixt <j6t@kdbg.org>
Date
May 24, 2016, 19:48 UTC
Message-ID
<5744B00D.4020006@kdbg.org>
In-Reply-To
<alpine.DEB.2.20.1605241510370.4449@virtualbox>
Am 24.05.2016 um 15:18 schrieb Johannes Schindelin:
Show 7 quoted lines
> Hannes, could you quickly test whether
> https://github.com/dscho/git/tree/interactive-rebase calls rerere twice,
> too? (Please call interactive rebase with the GIT_USE_REBASE_HELPER=true
> to avoid running the interactive rebase twice.)
>
> I have a hunch that it does not call rerere twice, which would be a nice
> bonus in that patch thicket
It prints the message only once:

gittest@master:1007> GIT_USE_REBASE_HELPER=true git rebase -i side error: could not apply fa62fea... master

When you have resolved this problem, run "git rebase --continue". If you prefer to skip this patch, run "git rebase --skip" instead. To check out the original branch and stop rebasing, run "git rebase --abort".

Recorded preimage for 'a' Could not apply fa62fea... mastergittest@master|REBASE-i 1/1:1008> 5~

(Take note of the missing LF at the end of the message.)

Can this result be interpreted as another indication that the "git rerere" call in die_with_patch can be removed, or are the two git-rebase implementations too different to be comparable?

-- Hannes
Previous: Johannes SchindelinNext: Johannes Schindelin
Message 6 of 11 in “Small rerere in rebase regression”
  1. Johannes SixtMay 23, 2016
  2. Junio C HamanoMay 23, 2016
  3. Johannes SixtMay 23, 2016
  4. Junio C HamanoMay 23, 2016
  5. Johannes SchindelinMay 24, 2016
  6. Johannes SixtMay 24, 2016
  7. Johannes SchindelinMay 25, 2016
  8. Johannes SchindelinMay 25, 2016
  9. Johannes SixtMay 27, 2016
  10. Johannes SchindelinMay 28, 2016
  11. Johannes SixtMay 24, 2016

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.