From: Taylor Blau <firstname.lastname@example.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Taylor Blau" <email@example.com>,
"Ævar Arnfjörð Bjarmason" <firstname.lastname@example.org>,
Subject: Re: js/bisect-in-c (was: What's cooking in git.git (Oct 2022, #09; Mon, 31))
Date: Thu, 10 Nov 2022 23:46:54 -0500 [thread overview]
Message-ID: <Y23Tvud88nwDm0Va@nand.local> (raw)
On Thu, Nov 10, 2022 at 02:35:26PM +0100, Johannes Schindelin wrote:
> So basically, I thought this was finally done and the next thing I hear is
> that it is ejected. That's quite a frustrating experience, I must admit.
> At least I am not a new contributor who would be very much deterred from
> contributing any further by such an experience.
I ejected the series for two reasons:
- it began to conflict with newer series that folks are working on,
- because I hadn't seen any activity on it from either you or any of
the previous reviewers.
I don't want to drop the topic on the floor if we are getting close to
or are at the finish line. *But*, there are a handful of other series in
flight which seem to conflict with this one.
It would have been much nicer to graduate this earlier, and certainly I
think some reviewer-signaling could have helped that.
But now that other topics have appeared, it would be nice to see a
rerolled version on top of any topic(s) with which it might conflict.
That, along with clear instructions of which topics it depends on will
help me queue it in the right order.
If it helps, I can try and take a closer look tomorrow when rebuilding
'seen' with the new topics. It may be possible for me to resolve the
conflicts with minimal effort. If it appears in 'seen', then you should
be OK, and we can start graduating this down. But if not, then having a
rerolled version would be very much appreciated.
next prev parent reply other threads:[~2022-11-11 4:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 5:31 What's cooking in git.git (Oct 2022, #09; Mon, 31) Taylor Blau
2022-10-31 23:44 ` ab/cmake-nix-and-ci (was: What's cooking in git.git (Oct 2022, #09; Mon, 31)) Ævar Arnfjörð Bjarmason
2022-10-31 23:45 ` ab/make-bin-wrappers " Ævar Arnfjörð Bjarmason
2022-10-31 23:46 ` ab/misc-hook-submodule-run-command " Ævar Arnfjörð Bjarmason
2022-11-01 0:15 ` Taylor Blau
2022-11-02 17:13 ` Ævar Arnfjörð Bjarmason
2022-11-02 17:24 ` Taylor Blau
2022-11-02 16:49 ` What's cooking in git.git (Oct 2022, #09; Mon, 31) Ramsay Jones
2022-11-02 17:22 ` js/bisect-in-c (was: What's cooking in git.git (Oct 2022, #09; Mon, 31)) Ævar Arnfjörð Bjarmason
2022-11-02 17:26 ` Taylor Blau
2022-11-10 13:35 ` Johannes Schindelin
2022-11-11 4:46 ` Taylor Blau [this message]
2022-11-11 14:11 ` Ævar Arnfjörð Bjarmason
2022-11-10 13:32 ` Johannes Schindelin
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:
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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 read-only IMAP folder(s) and NNTP newsgroup(s).