git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: git@vger.kernel.org
Subject: A note from the (interim) maintainer
Date: Fri, 11 Oct 2024 21:31:29 -0400	[thread overview]
Message-ID: <ZwnRcSrZhH9JdaS2@nand.local> (raw)

It is that time of year again where Junio takes a few very well
deserved weeks off. In the meantime, I'll be doing my best to fill in
the gaps as interim maintainer.

I'll follow the same process as Junio does, picking up topics from the
list and keeping things moving on the various integration branches.
I'll publish the broken-out topics to my fork at:

    git@github.com:ttaylorr/git.git

I'll keep the main integration branches up-to-date at the usual spot:

    git@github.com:git/git.git

, though like last time, the other mirrors (including kernel.org) will
lag behind. When Junio returns, he can push out the main integration
branches to the various mirrors to bring them back in-sync.

There is nothing new in either of those spots yet, besides syncing the
various in-flight branches from Junio's tree into my own, and dropping
old topics from a couple of years ago.

I'll keep up with new topics over the weekend, and push out a new
integration round on Monday. On Tuesday I'll send out a "What's
cooking" report.

If you have a topic in flight with no response, don't see it in my
tree, or it's absent from the next WC report, I might have missed it.
In that case, please nudge me or resend any missing topics.

Thanks,
Taylor

             reply	other threads:[~2024-10-12  1:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-12  1:31 Taylor Blau [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-10-28 23:43 A note from the (interim) maintainer Taylor Blau
2012-10-24  9:01 Jeff King

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=ZwnRcSrZhH9JdaS2@nand.local \
    --to=me@ttaylorr.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).