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

Re: [PATCH 1/1] Let rebase.reschedulefailedexec only affect interactive rebases

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jul 1, 2019, 11:49 UTC
Message-ID
<nycvar.QRO.7.76.6.1907011348280.44@tvgsbejvaqbjf.bet>
In-Reply-To
<xmqq4l498irq.fsf@gitster-ct.c.googlers.com>
Hi,
On Fri, 28 Jun 2019, Junio C Hamano wrote:
Show 7 quoted lines
> Phillip Wood <phillip.wood123@gmail.com> writes:
>
> > I was wondering about requiring --exec with --reschedule-failed-exec
> > rather than checking is_interactive() as that would be easier to
> > understand.
>
> ... I find this a reasonable way to think about the issue.

I don't: the `exec` command in interactive rebases' todo lists predates the `--exec` option by quite some time IIRC.

In other words, `--reschedule-failed-exec` can very well influence a `git rebase -i` without `--exec`.

Ciao, Dscho

Previous: Johannes SchindelinNext: Johannes Schindelin via GitGitGadget
Message 10 of 13 in “Make rebase.reschedulefailedexec less overzealous”
  1. 0/1 Make rebase.reschedulefailedexec less overzealousJohannes Schindelin via GitGitGadget, Jun 27, 2019
  2. 1/1 Let rebase.reschedulefailedexec only affect interactive rebasesJohannes Schindelin via GitGitGadget, Jun 27, 2019
  3. Junio C HamanoJun 27, 2019
  4. Johannes SchindelinJun 28, 2019
  5. Phillip WoodJun 28, 2019
  6. Junio C HamanoJun 28, 2019
  7. Vas SudanaguntaJun 28, 2019
  8. Phillip WoodJun 30, 2019
  9. Johannes SchindelinJul 1, 2019
  10. Johannes SchindelinJul 1, 2019
  11. 0/1 Make rebase.reschedulefailedexec less overzealousJohannes Schindelin via GitGitGadget, Jul 1, 2019
  12. 1/1 rebase --am: ignore rebase.reschedulefailedexecJohannes Schindelin via GitGitGadget, Jul 1, 2019
  13. Johannes SchindelinJul 1, 2019

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.