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

Re: Determining if a merge was produced automatically

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 1, 2024, 15:43 UTC
Message-ID
<xmqqh6d9yv66.fsf@gitster.g>
In-Reply-To
<ZoKXt0jPphoM5nmJ@google.com>
Jonathan Nieder <jrnieder@gmail.com> writes:
Show 8 quoted lines
>> However, this bit means that I shouldn't entirely trust its output:
>>
>>> The output emitted when this option is used is subject to change, and so is its interaction with other options (unless explicitly documented).
>>
>> What is my best course of action?
>
> I'd encourage proposing a patch to make the documentation say what you
> wish it said.

I do not think that was what Pavel wanted to get suggestion on, but it is certainly something that would benefit not just a single person but other users ;-)

Previous: Pavel RappoNext: Junio C Hamano
Message 4 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.