list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Taylor Blau <>
To: Junio C Hamano <>
Subject: Re: What's cooking in git.git (Nov 2022, #05; Tue, 22)
Date: Tue, 22 Nov 2022 18:35:49 -0500	[thread overview]
Message-ID: <Y31c1XZQn0RB+nrr@nand.local> (raw)
In-Reply-To: <xmqqfseargo4.fsf@gitster.g>

On Wed, Nov 23, 2022 at 03:24:27AM +0900, Junio C Hamano wrote:
> I have been offline for the last couple of weeks, but it seems that
> the development community have continued to thrive under Taylor's
> care.  Thanks for successfully concluding the "bus factor" exercise,
> everybody.  It will probably take me a few more days to catch up
> with what is in the tree right now and has been described in the
> previous few issues of the "What's cooking" report, and after that
> we will have -rc0 for the coming release.

Welcome back ;-).

Thanks very much for your trust over the past few weeks. It was a lot of
fun, and a lot of work, though having high-quality patches and lots of
review made it easy. I certainly have a new-found appreciation for how
much work goes into being the maintainer.

It would be nice to have more people be able to participate in the
bus-factor exercise in the future. Not just because it gives you a
break, and improves our chances of survival. But it also left me with a
sense of some good "do's" and "don't's" for how to be a better


      parent reply	other threads:[~2022-11-22 23:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-22 18:24 What's cooking in git.git (Nov 2022, #05; Tue, 22) Junio C Hamano
2022-11-22 19:01 ` gc/resolve-alternate-symlinks (Re: What's cooking in git.git (Nov 2022, #05; Tue, 22)) Glen Choo
2022-11-22 19:53   ` Jeff King
2022-11-22 23:06 ` ab/remove--super-prefix & ab/submodule-no-abspath (was: " Ævar Arnfjörð Bjarmason
2022-11-23  2:19   ` ab/remove--super-prefix & ab/submodule-no-abspath Junio C Hamano
2022-11-22 23:35 ` Taylor Blau [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:

  List information:

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

  git send-email \
    --in-reply-to=Y31c1XZQn0RB+nrr@nand.local \ \ \ \

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