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

Re: Determining if a merge was produced automatically

From
PRPavel Rappo <pavel.rappo@gmail.com>
Date
Jul 1, 2024, 16:43 UTC
Message-ID
<CAChcVu=5z2-Q=80zzzwY9eCV68=g-+uEy5u3Y94vb4-STKkRwQ@mail.gmail.com>
In-Reply-To
<CABPp-BG2p=0US9t-3DzPn8oCbPUXAg6HPciona8x8NNVyyowbw@mail.gmail.com>
On Mon, Jul 1, 2024 at 4:11 PM Elijah Newren <newren@gmail.com> wrote:
Show 8 quoted lines
> However, this wording was not intended to detract from the main point
> that "empty output means clean merge and non-empty output means
> conflicted merge" (it never even occurred to me that someone might
> read that part of the documentation and assume that it presents a
> problem for checking-if-diff-is-empty).  I use it for the same
> purpose, and that's absolutely a guarantee we want to provide.  If you
> want to guarantee output format beyond that, though, then I object.
>

That's good to know; thanks! Back to Jonathan's suggestion: I don't know how to express that in documentation. I cannot suggest any good wording at this time.

Previous: Elijah Newren
Message 11 of 11 in “Determining if a merge was produced automatically”
  1. Pavel RappoJun 30, 2024
  2. Jonathan NiederJul 1, 2024
  3. Pavel RappoJul 1, 2024
  4. Junio C HamanoJul 1, 2024
  5. Junio C HamanoJul 1, 2024
  6. Pavel RappoJul 1, 2024
  7. Junio C HamanoJul 1, 2024
  8. Pavel RappoJul 1, 2024
  9. Martin von ZweigbergkJul 1, 2024
  10. Elijah NewrenJul 1, 2024
  11. Pavel RappoJul 1, 2024

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.