From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2020, #01; Tue, 3)
Date: Tue, 03 Mar 2020 15:19:38 -0800 [thread overview]
Message-ID: <xmqqtv3558mt.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <xmqq1rq96nih.fsf@gitster-ct.c.googlers.com> (Junio C. Hamano's message of "Tue, 03 Mar 2020 15:12:54 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> Taylor Blau <me@ttaylorr.com> writes:
>
>> What's in 'v3' of that series [1] is ready to merge, in my opinion.
>
> Alright. Let's do so.
>
>> [1]: https://lore.kernel.org/git/cover.1581486293.git.me@ttaylorr.com/#t
>
> Thanks.
Hmph, actually...
> It was intended as the former, but I share both of your feelings that it
> could be read either way. I amended the commit message to clarify by
> adding:
>
> (and haven't since been deleted from the object store)
>
> as a parenthetical after "already in the graph...".
... don't we want to get that "amended" one, at least? I do not
recall if there were other things you said you'd tweak or not during
the review of that v3, though.
next prev parent reply other threads:[~2020-03-03 23:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 22:21 What's cooking in git.git (Mar 2020, #01; Tue, 3) Junio C Hamano
2020-03-03 23:05 ` Taylor Blau
2020-03-03 23:12 ` Junio C Hamano
2020-03-03 23:19 ` Junio C Hamano [this message]
2020-03-03 23:28 ` Taylor Blau
2020-03-04 3:31 ` Heba Waly
2020-03-04 15:30 ` Jonathan Tan
2020-03-04 16:18 ` Junio C Hamano
2020-03-05 15:17 ` Heba Waly
2020-03-06 17:23 ` [PATCH] update how-to-maintain-git Junio C Hamano
2020-03-06 19:06 ` Eric Sunshine
2020-03-06 21:28 ` Junio C Hamano
2020-03-07 12:16 ` Martin Ågren
2020-03-04 20:40 ` hv/receive-denycurrent-everywhere, was Re: What's cooking in git.git (Mar 2020, #01; Tue, 3) Johannes Schindelin
2020-03-04 21:27 ` 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=xmqqtv3558mt.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.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