Re: What's cooking in git.git (Sep 2023, #04; Tue, 12)

From: Philippe Blain <levraiphilippeblain@gmail.com>
Date: Sep 12, 2023, 21:13 UTC
Message-ID: <1B0BBA4A-7060-430E-A9ED-04470D9502DE@gmail.com>
In-Reply-To: <xmqq34zjnqi8.fsf@gitster.g>

Show 18 quoted lines

> Le 12 sept. 2023 à 15:25, Junio C Hamano <gitster@pobox.com> a écrit :
> 
>>> * pb/complete-commit-trailers (2023-09-07) 1 commit
>>>  (merged to 'next' on 2023-09-08 at 842587016d)
>>> + completion: commit: complete configured trailer tokens
>>> 
>>> The command-line complation support (in contrib/) learned to
>>> complete "git commit --trailer=" for possible trailer keys.
>>> 
>>> Will merge to 'master'.
>>> source: <pull.1583.git.1694108551683.gitgitgadget@gmail.com>
>>> 
>> 
>> I've incorporate Martin's suggestions so let's wait to merge my v2 
>> instead:
>> <pull.1583.v2.git.1694539827.gitgitgadget@gmail.com>
> 
> It is too late for a replacement v2 once it is in 'next', though.

Yes of course, this v2 has a second commit on top of top of v1 since v1 was already in next. Maybe my wording was unclear ? Or do you prefer a new thread for such fix ups ?

Thanks, Philippe.