From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Shawn O. Pearce" <spearce@spearce.org>, git@vger.kernel.org
Subject: Re: Interim maintainer tree
Date: Sun, 4 Oct 2009 02:41:29 -0400 [thread overview]
Message-ID: <20091004064129.GB7076@coredump.intra.peff.net> (raw)
In-Reply-To: <7viqevu1zt.fsf@alter.siamese.dyndns.org>
On Sat, Oct 03, 2009 at 11:06:30PM -0700, Junio C Hamano wrote:
> Thanks, both.
>
> I've fetched, but haven't fully examined "log ..spearce/*" nor "log ..peff/*"
> yet.
>
> I noticed that some topics in 'pu' have been rebased (not complaining, but
> just making sure I am not hallucinating).
>
> Do you have preferences/suggestions as to how to proceed? Should I just
> take the tips over at this point, or do you have some more patches you
> were polishing but haven't pushed out that I should wait for?
For my stuff, I think you can just take over my tips. I was just
collecting and polishing topics, while Shawn was doing integration. For
topics I have, please use my versions rather than applying from the
list; many of them have extra fixes squashed in, acked-by's collected
from the list, etc.
Here's a brief status report on what's in my tree:
proposed-master
One-off patches that I think should go straight to master.
ef/mscv-noreturn
This is the latest round and I think should be ready for at least
'next' (maybe even 'master' as it is really about the build and not
about functionality).
ef/msys-imap
This is from an RFC which has generated some comments. He should be
posting another round soon. 'pu' at best.
fc/mutt-alias
Latest round that addressed comments. Ready for 'next' if not
'master'.
jn/gitweb-patch
After some comments with Jakub, I think the code is right but he
promised a re-roll with more in the commit message.
mr/gitweb-snapshot
This is probably the pu rewind you saw. He posted a v5 of his
series. I didn't look at it closely, but Jakub ack'd it.
tf/doc-pt-br
Minor translation update, ack'd by somebody who can read it. :)
Ready for 'master'.
There are a few patches floating on the list that I haven't picked up or
looked too closely at yet. Just so we don't drop anything, they are:
- curl http auth tweak:
http://article.gmane.org/gmane.comp.version-control.git/129455
The author said he didn't really test it, and I haven't set up http
auth to test it with, but probably somebody should do so before
applying. :)
- a new rev-cache from Nick
- silence gcc warning:
http://article.gmane.org/gmane.comp.version-control.git/129485
The warning is overly cautious, I think, but it is a dubious enough
construct that it is probably worth fixing.
- enable openssl on msvc
http://article.gmane.org/gmane.comp.version-control.msysgit/7238
This goes on top of ef/msys-imap, but I think that will be getting a
re-roll.
-Peff
next prev parent reply other threads:[~2009-10-04 7:05 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 [this message]
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=20091004064129.GB7076@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).