From: Junio C Hamano <gitster@pobox.com>
To: Philippe Blain <levraiphilippeblain@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2023, #04; Tue, 12)
Date: Tue, 12 Sep 2023 12:25:03 -0700 [thread overview]
Message-ID: <xmqq34zjnqi8.fsf@gitster.g> (raw)
In-Reply-To: <2579735c-d0cd-d159-8cdb-3348c808b9ef@gmail.com> (Philippe Blain's message of "Tue, 12 Sep 2023 13:32:17 -0400")
Philippe Blain <levraiphilippeblain@gmail.com> writes:
> Hi Junio,
>
> Le 2023-09-12 à 12:57, Junio C Hamano a écrit :
>
>> * pb/completion-aliases-doc (2023-09-11) 1 commit
>> - completion: improve doc for complex aliases
>>
>> Clarify how "alias.foo = : git cmd ; aliased-command-string" should
>> be spelled with necessary whitespaces around punctuation marks to
>> work.
>>
>> Will merge to 'next'.
>> source: <pull.1585.git.1694274592854.gitgitgadget@gmail.com>
>
> Thanks, I just sent a v2 so let's make sure this is what you merge:
> <pull.1585.v2.git.1694538135853.gitgitgadget@gmail.com>
OK. Thanks for a heads-up _before_ it hits 'next'.
>> * 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.
next prev parent reply other threads:[~2023-09-12 19:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 16:57 What's cooking in git.git (Sep 2023, #04; Tue, 12) Junio C Hamano
2023-09-12 17:32 ` Philippe Blain
2023-09-12 19:25 ` Junio C Hamano [this message]
2023-09-12 21:13 ` Philippe Blain
2023-09-12 18:30 ` Phillip Wood
2023-09-12 19:34 ` Junio C Hamano
2023-09-12 17:07 Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq34zjnqi8.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=levraiphilippeblain@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).