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

Re: git format-patch with useAutoBase = true

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 15, 2020, 20:24 UTC
Message-ID
<xmqqzh5qzt3d.fsf@gitster.c.googlers.com>
In-Reply-To
<CA+P7+xpjSxEmB0qpWkhkd=yeA9xF-ssVdW1J5NyJdkqfza=GPg@mail.gmail.com>
Jacob Keller <jacob.keller@gmail.com> writes:
Show 7 quoted lines
> $  git format-patch -1 f7529b4ba3c98470b0e367ba447ad0da84dc308
> fatal: base commit shouldn't be in revision list
> ...
> The failure occurs because the "automatic" base is newer than the
> requested commit. I am wondering if it would make sense to relax this
> restriction and make the format-patch automatically disable
> useAutoBase if it would conflict like this?

I agree that it does make a horrible end-user experience to die with the message like the above, trying to use a nonsense autobase.

Previous: Jacob Keller
Message 2 of 2 in “git format-patch with useAutoBase = true”
  1. Jacob KellerSep 15, 2020
  2. Junio C HamanoSep 15, 2020

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.