git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: Interim maintainer tree
Date: Sun, 27 Sep 2009 04:54:37 -0400	[thread overview]
Message-ID: <20090927085437.GA10828@coredump.intra.peff.net> (raw)
In-Reply-To: <20090925160504.GW14660@spearce.org>

On Fri, Sep 25, 2009 at 09:05:04AM -0700, Shawn O. Pearce wrote:

> 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

I've collected a few more topics in my repo:

  git://github.com/peff/git.git

Rather than cook my own, slightly different 'next', I'm just publishing
the tips of the topics themselves. Which means they are subject to
rewinding until you merge them into 'next', at which point I will leave
them stable.

What's in there now is:

  as/parseopt-ambiguous
    Fix for "git branch --no-merge" with my test added. Should be ready
    for next.

  jk/reflog-date
    My reflog fix. Should be ready for next.

  mr/gitweb-snapshot
    v5, replacing what Junio had in pu. Should probably stay in pu until
    we hear from Jakub.

  mr/instaweb
    Looked OK to me, but I have no capacity to actually test it.
    Unlikely to break anything else, though, so probably ready to cook
    in next.

  mv/lock-error
    My tweaked version, which got the OK from Miklos. Ready for next, I
    think.

  np/clone-smaller
    Nico's fix to stop copying unnecessary objects during clone. Patch
    looks sane, I confirmed that it fixes the issue, and it doesn't seem
    to break normal clones. Ready to cook in next, I think.

-Peff

  reply	other threads:[~2009-09-27  8:54 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 [this message]
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
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=20090927085437.GA10828@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.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).