From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: Interim maintainer tree
Date: Mon, 5 Oct 2009 07:56:15 -0700 [thread overview]
Message-ID: <20091005145615.GA9261@spearce.org> (raw)
In-Reply-To: <7viqevu1zt.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> wrote:
> "Shawn O. Pearce" <spearce@spearce.org> writes:
> > Junio is on vaction for the next week. In his absence Peff and I
> > are trying to keep up with current patches in my fork:
> >
> > git://repo.or.cz/git/spearce.git
> > http://repo.or.cz/r/git/spearce.git
> >
> > Right now the tree matches Junio's last push, I'll try to pick up
> > the patches since then and push later today.
>
> Thanks, both.
>
> I've fetched, but haven't fully examined "log ..spearce/*" nor "log ..peff/*"
> yet.
Sorry, I proved to be a very poor interim maintainer this cycle.
I just didn't have the time to keep up with integration each day,
and then dropped the ball on Thursday and Friday and failed to pull
anything from Peff or the list. Peff, thanks for keeping up a bit
and at least having some tips for Junio to pick up from.
> I noticed that some topics in 'pu' have been rebased (not complaining, but
> just making sure I am not hallucinating).
Yes, some topics in 'pu' got rebased. Wednesday I ran RB
after preparing a new master, and then rebuilt pu around it.
Unfortunately I somehow lost a patch on Nick's rev-list series,
not sure how I managed to do that, but I guess I did, sorry.
Were you no longer in the habit of running RB when you rebuilt pu?
--
Shawn.
next prev parent reply other threads:[~2009-10-05 15:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 16:05 Interim maintainer tree Shawn O. Pearce
2009-09-27 8:54 ` Jeff King
2009-10-04 6:06 ` Junio C Hamano
2009-10-04 6:41 ` Jeff King
2009-10-04 9:54 ` Junio C Hamano
2009-10-04 13:29 ` Jeff King
2009-10-05 14:56 ` Shawn O. Pearce [this message]
2009-10-05 15:05 ` 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=20091005145615.GA9261@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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).