From: Philippe Blain <levraiphilippeblain@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2023, #02; Tue, 6)
Date: Sun, 11 Jun 2023 11:15:00 -0400 [thread overview]
Message-ID: <5cd3a92c-0f7c-5bf5-7706-753ad00441d2@gmail.com> (raw)
In-Reply-To: <xmqq5y814aw8.fsf@gitster.g>
Hi Junio,
Le 2023-06-05 à 21:50, Junio C Hamano a écrit :
> * pb/complete-and-document-auto-merge-and-friends (2023-05-23) 6 commits
> - completion: complete AUTO_MERGE
> - Documentation: document AUTO_MERGE
> - git-merge.txt: modernize word choice in "True merge" section
> - completion: complete REVERT_HEAD and BISECT_HEAD
> - revisions.txt: document more special refs
> - revisions.txt: use description list for special refs
>
> Document more pseudo-refs and teach the command line completion
> machinery to complete AUTO_MERGE.
>
> Kicked back to 'seen' and replaced.
> Needs review/ack.
> source: <pull.1515.v2.git.1684783741.gitgitgadget@gmail.com>
Elijah reviewed the new version in [1], to which you responded in [2].
So from what I understand we are just waiting for 'next' to be rebuilt,
not for additional reviews, right?
Thanks,
Philippe.
[1] CABPp-BH+vT_dEKUwn1M2D-FuCtF=hRM8OAFj9m1x6rkV97oEDA@mail.gmail.com/
[2] https://lore.kernel.org/git/xmqqwn0nab9n.fsf@gitster.g/
next prev parent reply other threads:[~2023-06-11 15:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 1:50 What's cooking in git.git (Jun 2023, #02; Tue, 6) Junio C Hamano
2023-06-06 9:15 ` Kristoffer Haugsbakk
2023-06-12 17:53 ` Junio C Hamano
2023-06-06 13:35 ` Derrick Stolee
2023-06-12 17:55 ` Junio C Hamano
2023-06-11 15:15 ` Philippe Blain [this message]
2023-06-12 17:56 ` 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=5cd3a92c-0f7c-5bf5-7706-753ad00441d2@gmail.com \
--to=levraiphilippeblain@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).