From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Jonathan Nieder <jrnieder@gmail.com>
Subject: 1.7.2 cycle will open soon
Date: Tue, 04 May 2010 22:39:59 -0700 [thread overview]
Message-ID: <7vaaselxe8.fsf@alter.siamese.dyndns.org> (raw)
The usual post-release ritual.
- The tip of 'next' has been rebuilt on top of the release, with topics
that have been cooking;
- The 'maint' branch is now for 1.7.1.X series; and
- What have been cooking in 'next' during the pre-release freeze period
for 1.7.1 should start graduating to 'master' soon.
It appears that the tip of 'maint' and 'next' (but curiously not 'master')
do not pass test t1504 on at least FreeBSD right now, but I don't have
enough energy to hunt things down tonight.
next reply other threads:[~2010-05-05 5:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 5:39 Junio C Hamano [this message]
2010-05-06 5:52 ` 1.7.2 cycle will open soon Jeff King
2010-05-06 6:44 ` Jonathan Nieder
2010-05-06 6:54 ` Jeff King
2010-05-06 8:41 ` [PATCH] test-lib: some shells do not let $? propagate into an eval Jonathan Nieder
2010-05-06 8:57 ` Jeff King
2010-05-06 20:20 ` Junio C Hamano
2010-05-06 7:06 ` 1.7.2 cycle will open soon Johannes Sixt
2010-05-06 7:49 ` Jeff King
2010-05-06 8:01 ` Jonathan Nieder
2010-05-06 6:57 ` Johannes Sixt
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=7vaaselxe8.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
/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).