Re: [PATCH v1 0/9] diff-merges: let -m imply -p

From: Sergey Organov <sorganov@gmail.com>
Date: May 17, 2021, 20:11 UTC
Message-ID: <875yzhf7cq.fsf@osv.gnss.ru>
In-Reply-To: <xmqq1ra56svo.fsf@gitster.g>

Junio C Hamano <gitster@pobox.com> writes:

Show 11 quoted lines

> Sergey Organov <sorganov@gmail.com> writes:
>
>> Fix long standing inconsistency between -c/--cc that do imply -p, on
>> one side, and -m that did not imply -p, on the other side.
>> ...
>> Exact historical semantics of -m is still provided by
>> --diff-merges=separate.
>>
>> Updates in v1:
>
> OK, so this is [v2] not v1 ;-)

I dunno. Actually, I'm a bit confused.

Is simple [PATCH] v0 or v1? For me, as C-programmer, it's obviously v0, and that's what

  git format-patch --reroll-count=0
 
produces anyway, and the next one is

  git format-patch --reroll-count=1

that produces [PATCH v1]. That's how it became v1.

>
> Will replace.  Thanks.

Thanks!

-- Sergey Organov

$ 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.