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 13:35:23 -0700 [thread overview]
Message-ID: <xmqqy1iua4c4.fsf@gitster.g> (raw)
In-Reply-To: <CAJoAoZngMcN-0-5q1y-zX5552QhgRHCrKULQ7hKyJgcCoSQJNQ@mail.gmail.com> (Emily Shaffer's message of "Tue, 1 Aug 2023 13:27:33 -0700")
Emily Shaffer <nasamuffin@google.com> writes:
>> Or are there still further changes in behaviours planned?
>
> Huh, I thought that you wanted further changes. In
> https://lore.kernel.org/git/ZDSTFwMFO7vbj%2Fdu@google.com/ I was
> asking for opinions on adding tests; if you're fine to take it without
> tests, then of course I don't have an objection to an identical patch
> with objectively improved grammar in the commit message. But since you
> were asking for a reroll in the What's Cooking, I figured there was
> more you were unhappy with in the patch. If that's not the case, by
> all means, go ahead and take it.
Well, this is why an overly slow reaction is bad for everybody.
I quite honestly do not recall what was suggested and with what
severity (was it a good to have? was it a showstopper?).
Anyway, if it is not urgent and nobody else is jumping up and down
and asking for an immediate inclusion of the current iteration, we
can wait a bit longer without hurting anybody ;-)
Thanks.
prev parent reply other threads:[~2023-08-01 20:35 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
2023-08-01 20:27 ` Emily Shaffer
2023-08-01 20:35 ` Junio C Hamano [this message]
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=xmqqy1iua4c4.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 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.