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

Re: RFC: indicating diff strategy in format-patch message headers

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 5, 2024, 18:22 UTC
Message-ID
<xmqq5xuns10v.fsf@gitster.g>
In-Reply-To
<20240605-hilarious-dramatic-mushroom-7fd941@lemur>
Konstantin Ryabitsev <konstantin@linuxfoundation.org> writes:
> Would it make sense to have git-format-patch (and friends) include an
> additional header hinting at the options used to generate the patch? E.g.:
>
>     X-git-diff-options: algo=myers; context=3;

I doubt it. And newer version of Git _will_ try to improve how patch text appears to be more useful to human users, so you have more moving parts than you'd want to even think about enumerating.

If you were to add a new e-mail header, wouldn't it make more sense to add a patch-id header and agree on the set of options to be used to generate that patch-id (which might be different from the setting used to format the real patch for human and "git am" consumption)?

Previous: Konstantin RyabitsevNext: Konstantin Ryabitsev
Message 2 of 6 in “RFC: indicating diff strategy in format-patch message headers”
  1. Konstantin RyabitsevJun 5, 2024
  2. Junio C HamanoJun 5, 2024
  3. Konstantin RyabitsevJun 5, 2024
  4. Eric WongJun 5, 2024
  5. Konstantin RyabitsevJun 7, 2024
  6. Eric WongJun 16, 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.