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

Re: Determining if a merge was produced automatically

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Jul 1, 2024, 11:49 UTC
Message-ID
<ZoKXt0jPphoM5nmJ@google.com>
In-Reply-To
<CAChcVu=Kwqj7JhXqQW6Ni9+3TdSfdmHfSTJQWm1_uO2kczSm8g@mail.gmail.com>
Hi Pavel,
Pavel Rappo wrote:
Show 5 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. What guarantees would you like it to make? That will help with others in the project being able to decide what it should guarantee and what it shouldn't, and regardless of the outcome of discussion it would make the documentation more helpful for the next person.

See Documentation/MyFirstContribution for some more details on how proposing a patch works.

Thanks and hope that helps, Jonathan

Previous: Pavel RappoNext: Pavel Rappo
Message 2 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.