git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Interim maintainer tree

From
Jeff King <peff@peff.net>
Date
Sep 27, 2009, 08:54 UTC
Message-ID
<20090927085437.GA10828@coredump.intra.peff.net>
In-Reply-To
<20090925160504.GW14660@spearce.org>
On Fri, Sep 25, 2009 at 09:05:04AM -0700, Shawn O. Pearce wrote:
Show 5 quoted lines
> 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
Previous: Shawn O. PearceNext: Junio C Hamano
Message 2 of 8 in “Interim maintainer tree”
  1. Shawn O. PearceSep 25, 2009
  2. Jeff KingSep 27, 2009
  3. Junio C HamanoOct 4, 2009
  4. Jeff KingOct 4, 2009
  5. Junio C HamanoOct 4, 2009
  6. Jeff KingOct 4, 2009
  7. Shawn O. PearceOct 5, 2009
  8. Jeff KingOct 5, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.