From: Junio C Hamano <gitster@pobox.com>
To: Emily Shaffer <nasamuffin@google.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2023, #07; Mon, 31)
Date: Tue, 01 Aug 2023 11:12:27 -0700 [thread overview]
Message-ID: <xmqqzg3abpis.fsf@gitster.g> (raw)
In-Reply-To: <CAJoAoZk1WiCSDqFXccG4FiwYhWUuWWmFz+ZqiXhacmfjZuE6FA@mail.gmail.com> (Emily Shaffer's message of "Tue, 1 Aug 2023 10:38:17 -0700")
Emily Shaffer <nasamuffin@google.com> writes:
> On Mon, Jul 31, 2023 at 10:57 AM Junio C Hamano <gitster@pobox.com> wrote:
>> * es/recurse-submodules-option-is-a-bool (2023-04-10) 1 commit
>> . usage: clarify --recurse-submodules as a boolean
>>
>> The "--[no-]recurse-submodules" option of "git checkout" and others
>> supported an undocumented syntax --recurse-submodules=<value> where
>> the value can spell a Boolean in various ways. The support for the
>> syntax is being dropped.
>>
>> Have been expecting a reroll for too long.
>> cf. <ZDSTFwMFO7vbj/du@google.com>
>> source: <ZDSTFwMFO7vbj/du@google.com>
>
> Yeah, sorry about the annoying wait. It's not something I have time to
> reroll soon - but it's on the short list for "up next" bugs for my
> team to get a reroll. We still intend to reroll and push through, but
> I don't have an ETA. I'll leave it up to you to decide whether to keep
> it in seen or drop it with that information.
I actually do not quite understand this ;-) It wouldn't take more
than 20 seconds to read the "minimally touched-up version" sent
months ago https://lore.kernel.org/git/xmqqfs97cozz.fsf@gitster.g/
and say "yeah, that is perfect and please queue with the fixup" ;-)
Or are there still further changes in behaviours planned?
Thanks.
next prev parent reply other threads:[~2023-08-01 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 17:57 What's cooking in git.git (Jul 2023, #07; Mon, 31) Junio C Hamano
2023-08-01 17:38 ` Emily Shaffer
2023-08-01 18:12 ` Junio C Hamano [this message]
2023-08-01 20:27 ` Emily Shaffer
2023-08-01 20:35 ` 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=xmqqzg3abpis.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=nasamuffin@google.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).