From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Jeff King <peff@peff.net>
Subject: Re: What's cooking in git.git (Nov 2012, #03; Tue, 13)
Date: Tue, 13 Nov 2012 14:57:28 -0800 [thread overview]
Message-ID: <7vobj1cdrb.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20121113175205.GA26960@sigill.intra.peff.net> (Jeff King's message of "Tue, 13 Nov 2012 12:52:06 -0500")
Jeff King <peff@peff.net> writes:
> What's cooking in git.git (Nov 2012, #03; Tue, 13)
> --------------------------------------------------
>
> Here are the topics that have been cooking. Commits prefixed with
> '-' are only in 'pu' (proposed updates) while commits prefixed with
> '+' are in 'next'.
>
> This is my final "what's cooking" as interim maintainer. I didn't
> graduate anything to master, but I updated my plans for each topic to
> give Junio an idea of where I was.
>
> You can find the changes described here in the integration branches of
> my repository at:
>
> git://github.com/peff/git.git
>
> Until Junio returns, kernel.org and the other "usual" places will not be
> updated.
And now the "usual places" have been updated with the same tips of
integration branches (the broken-out https://github.com/gitster/git
repository, too).
prev parent reply other threads:[~2012-11-13 22:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 17:52 What's cooking in git.git (Nov 2012, #03; Tue, 13) Jeff King
2012-11-13 20:01 ` Junio C Hamano
2012-11-13 20:45 ` Torsten Bögershausen
2012-11-13 20:48 ` Pyeron, Jason J CTR (US)
2012-11-14 1:18 ` Mark Levedahl
2012-11-14 19:02 ` Jeff King
2012-11-14 21:13 ` Torsten Bögershausen
2012-11-15 0:16 ` Jeff King
2012-11-15 0:19 ` Junio C Hamano
2012-11-15 1:50 ` Mark Levedahl
2012-11-15 1:56 ` Jeff King
2012-11-15 5:54 ` Torsten Bögershausen
2012-11-16 18:52 ` Junio C Hamano
2012-11-17 7:11 ` Torsten Bögershausen
2012-11-15 19:05 ` Ramsay Jones
2012-11-15 19:35 ` Torsten Bögershausen
2012-11-15 23:34 ` Mark Levedahl
2012-11-13 22:57 ` Junio C Hamano [this message]
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=7vobj1cdrb.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--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).