archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <>
To: "Ævar Arnfjörð Bjarmason" <>
	"brian m. carlson" <>,
	Jeff King <>, Eric Wong <>
Subject: Re: What's cooking in git.git (Apr 2021, #05; Mon, 19)
Date: Tue, 20 Apr 2021 16:51:58 -0700	[thread overview]
Message-ID: <xmqqk0ow1plt.fsf@gitster.g> (raw)
In-Reply-To: <> (=?utf-8?B?IsOGdmFyIEFy?= =?utf-8?B?bmZqw7Zyw7A=?= Bjarmason"'s message of "Tue, 20 Apr 2021 15:52:33 +0200")

Ævar Arnfjörð Bjarmason <> writes:

> On Tue, Apr 20 2021, Junio C Hamano wrote:
> Comments on my outstanding serieses and related (you've indicated that
> this summary was helpful, so I'll keep doing it).
>> * ab/unexpected-object-type (2021-04-14) 11 commits
>> ...
> I've just re-rolled these three at:
>  *
>  *
>  *

Unfortunately, I didn't get to these three.  In the meantime, I'd
expect you to try merging these three into 'seen' once it gets
published today, and invite others who have topics not in 'next' but
in 'seen' to also do so.  By doing so, you'd see what interactions,
if any, are expected with the other topics in-flight.  I'd hope them
to be minimal---the old ab/unexpected-object-type had only one "yes,
that might be nice standalone if you are not working together with
other people, but we didn't have to make this change and we would
have saved having to do an evil merge to resolve this conflict if we
didn't"---as the old topic is tenatively ejected, the evil merge is
gone for now from 'seen', which is good ;-).

Anyway, without these three, but with the few topics that depends on
updated test-lib-updates topioc, the integration of the topics in
'seen' for today's cycle has been smooth.  The test-lib-updates
still had the same few niggles in its early parts I pointed out in
an earlier round, though.  Among the topics from you, I'd think that
one would be the highest priority, simply because many other topics
are taken hostage to it.  It matters to me a lot, as I'd be the one
who ends up having to remember what depends on what else, and having
to rebase them on top of each other.  The sooner that topic solidifies,
the better for other topics that depend on it.


  parent reply	other threads:[~2021-04-20 23:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-19 23:25 Junio C Hamano
2021-04-20 13:23 ` Matheus Tavares Bernardino
2021-04-20 13:52 ` Ævar Arnfjörð Bjarmason
2021-04-20 22:15   ` Junio C Hamano
2021-04-20 23:14   ` brian m. carlson
2021-04-21  8:26     ` Ævar Arnfjörð Bjarmason
2021-04-21 22:32       ` brian m. carlson
2021-04-20 23:51   ` Junio C Hamano [this message]
2021-04-23 14:41   ` Jeff King
2021-04-20 14:28 ` Jeff Hostetler

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqk0ow1plt.fsf@gitster.g \ \ \ \ \ \ \
    --subject='Re: What'\''s cooking in git.git (Apr 2021, #05; Mon, 19)' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).