From: "Joachim Schmitz" <jojo@schmitz-digital.de>
To: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2012, #05; Fri, 14)
Date: Sat, 15 Sep 2012 12:08:27 +0200 [thread overview]
Message-ID: <k31k35$pc$1@ger.gmane.org> (raw)
In-Reply-To: 7vboh82t7p.fsf@alter.siamese.dyndns.org
Junio C Hamano wrote:
> I think we can start thinking about feature freeze once the topics
> in 'next' that are scheduled to graduate to 'master' already are
> fully cooked. For any late-coming topic, there always is the next
> cycle ;-)
I've not hear anything about my poll patches and I'd really like them to
into 1.8.x.
If and when they did, there's another small patch to fully support HP
NonStop (some adjustment to git-compat-util.h with #ifdef __TANDEM and a
NonStop section in Makefile, so nothing that should have any bad impact on
others), which I too would like to get in 1.8.x
Bye, Jojo
next prev parent reply other threads:[~2012-09-15 10:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 21:24 What's cooking in git.git (Sep 2012, #05; Fri, 14) Junio C Hamano
2012-09-15 10:08 ` Joachim Schmitz [this message]
2012-09-15 17:01 ` Junio C Hamano
2012-09-15 17:15 ` Joachim Schmitz
2012-09-17 7:19 ` Joachim Schmitz
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='k31k35$pc$1@ger.gmane.org' \
--to=jojo@schmitz-digital.de \
--cc=git@vger.kernel.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).