All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Fabian Stelzer" <fs@gigacodes.de>
Cc: Carlo Arenas <carenas@gmail.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2021, #01; Thu, 2)
Date: Tue, 07 Sep 2021 10:39:33 -0700	[thread overview]
Message-ID: <xmqq35qgcmju.fsf@gitster.g> (raw)
In-Reply-To: <xmqq8s09e5i0.fsf@gitster.g> (Junio C. Hamano's message of "Mon, 06 Sep 2021 14:52:39 -0700")

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

> Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>
>> On Mon, Sep 06 2021, Carlo Arenas wrote:
>>
>>>> * fs/ssh-signing (2021-08-29) 9 commits
>>...
>>     I'm also interested in this one. My reading of
>>     <9075cdd1-e34d-5dcb-f2b8-69ae4abf587b@gigacodes.de> is that the author
>>     plans to re-roll it sometimes around mid-September. I personally punted
>>     on reviewing the current version while waiting for that.
>
> Ouch.  Let's eject it and wait for the promised reroll, then.

Actually, let's not do so immediately.  As I wrote in
https://lore.kernel.org/git/xmqq4kawcmqg.fsf@gitster.g/ I'd like to
wait and decide after seeing how big the fix need to be.

Thanks.

  reply	other threads:[~2021-09-07 17:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-02 22:48 What's cooking in git.git (Sep 2021, #01; Thu, 2) Junio C Hamano
2021-09-03  0:59 ` Philippe Blain
2021-09-03  4:38   ` Junio C Hamano
2021-09-03  2:25 ` Taylor Blau
2021-09-03  4:38   ` Junio C Hamano
2021-09-06  8:55 ` Carlo Arenas
2021-09-06 10:02   ` Ævar Arnfjörð Bjarmason
2021-09-06 21:52     ` Junio C Hamano
2021-09-07 17:39       ` Junio C Hamano [this message]
2021-09-06 10:36 ` Han-Wen Nienhuys
2021-09-06 21:55   ` Junio C Hamano
2021-09-06 22:21     ` Ævar Arnfjörð Bjarmason
2021-09-07 10:13 ` Ævar Arnfjörð Bjarmason
2021-09-07 17:15   ` 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=xmqq35qgcmju.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=carenas@gmail.com \
    --cc=fs@gigacodes.de \
    --cc=git@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.