From: Junio C Hamano <gitster@pobox.com>
To: Glen Choo <chooglen@google.com>
Cc: git@vger.kernel.org, Calvin Wan <calvinwan@google.com>
Subject: Re: cw/header-compat-util-shuffle (was Re: What's cooking in git.git (Jun 2023, #07; Tue, 27))
Date: Wed, 28 Jun 2023 15:31:42 -0700 [thread overview]
Message-ID: <xmqqilb7b4mp.fsf@gitster.g> (raw)
In-Reply-To: <kl6ledlvqo94.fsf@chooglen-macbookpro.roam.corp.google.com> (Glen Choo's message of "Wed, 28 Jun 2023 14:18:47 -0700")
Glen Choo <chooglen@google.com> writes:
>> Yes, I have found that it had too many bad interactions with topics
>> in flight and, keeping it out of 'seen' was very much deliberate.
>
> Thanks, that makes sense.
>
> Perhaps it should still get a call out in What's Cooking? When Calvin
> referenced that series, I went digging in What's Cooking for the topic
> name, and when I couldn't find it, I manually listed the topic branches
> starting with "cw/"; fortunately, Calvin's contribution history is short
> enough to make that tenable ;)
Maybe.
As I only have limited bandwidth, I do not know how stale the posted
version got since other topics in flight also moved. It may be that
other topics have graduated to 'master' and the conflicts got even
worse but it can be easier to resurrect on top of updated 'master'.
Or other topics that had interactions somehow magically stopped
being conflicting. Or the series by itself may have remaining
issues pointed out during the review and is not ready to be picked
up. I truly do not know. Sorry.
One thing that many contributors are doing, which is very much
appreciated, is make sure that the series they are going to post
would work well with at least the tip of 'next' and also with
'seen', as well as 'master', before sending them out. It would help
everybody: those who own topics that the series interacts with, the
maintainer, and those who may want to build on top of what the
series adds.
If the topic is too disruptive, however, they may have to synthesize
a good base (i.e. "merge on top of 'master' topics A, B and C, and
then queue these patches") but it may not be possible (e.g. among
the topics it interacts with, some topic may not yet be stable to
build on), in which case they must catch up quickly every time these
other topics it depends on are updated to avoid being left behind.
If the contributor cannot afford the time for quicker turnaround
that way, it would very much help everybody to announce that they
tentatively withdraw the topic until the other topics get more
stable, after which time they will send an updated version. It
will help everybody, including those who want to build on top of
what the series adds.
Thanks.
next prev parent reply other threads:[~2023-06-28 22:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 22:11 What's cooking in git.git (Jun 2023, #07; Tue, 27) Junio C Hamano
2023-06-28 9:54 ` Teng Long
2023-06-28 16:24 ` Junio C Hamano
2023-06-28 19:29 ` cw/header-compat-util-shuffle (was Re: What's cooking in git.git (Jun 2023, #07; Tue, 27)) Glen Choo
2023-06-28 21:03 ` Junio C Hamano
2023-06-28 21:18 ` Glen Choo
2023-06-28 22:31 ` Junio C Hamano [this message]
2023-06-28 22:47 ` Junio C Hamano
2023-06-28 23:58 ` What's cooking in git.git (Jun 2023, #07; Tue, 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=xmqqilb7b4mp.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=calvinwan@google.com \
--cc=chooglen@google.com \
--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 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).