From: "Shawn O. Pearce" <spearce@spearce.org>
To: git@vger.kernel.org
Subject: A note from the interim Git maintainer
Date: Wed, 24 Sep 2008 08:46:32 -0700 [thread overview]
Message-ID: <20080924154632.GR3669@spearce.org> (raw)
As mentioned recently by Junio, Junio is away on family leave and
a much deserved vacation until ~Oct 6th. Until he gets back I am
offering up my services as patch monkey to keep us moving along.
My tree is being published here:
git: git://repo.or.cz/git/spearce.git
repo.or.cz/srv/git/git/spearce.git
http://repo.or.cz/r/git/spearce.git
gitweb: http://repo.or.cz/w/git/spearce.git
The usual maint/master/next/pu stuff applies. I'm basically just
picking up from where Junio left off.
I would appreciate it if anyone who normally tracks Junio's "next"
or "master" branch for their production work can switch over to my
next (or master) branch for the next few weeks. Something about
many eyeballs and fewer bugs.
Patches can be CC'd to me, or just sent to the list. If I have
dropped something, please feel free to give me a gentle prod.
I know that I am quite behind on git-gui patches. I think I'm going
to spend the better part of today just on Git to get everything
caught up.
--
Shawn.
next reply other threads:[~2008-09-24 15:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 15:46 Shawn O. Pearce [this message]
2008-09-26 13:24 ` A note from the interim Git maintainer Mike Ralphson
2008-09-26 22:54 ` Jeff King
2008-09-29 7:51 ` Mike Ralphson
2008-10-01 7:16 ` obscure platform autobuilders Jeff King
2008-10-01 10:46 ` Mike Ralphson
2008-10-01 15:37 ` Jeff King
-- strict thread matches above, loose matches on Subject: below --
2007-10-16 5:54 A note from the interim Git maintainer Shawn O. Pearce
2007-10-17 6:31 ` Eric Wong
2007-10-17 7:13 ` Shawn O. Pearce
2007-10-18 3:03 ` Eric Wong
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
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 \
--in-reply-to=20080924154632.GR3669@spearce.org \
--to=spearce@spearce.org \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).