From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: Ready for 1.6.6-rc2?
Date: Wed, 09 Dec 2009 13:54:26 -0800 [thread overview]
Message-ID: <7vws0vn78t.fsf@alter.siamese.dyndns.org> (raw)
I see many people have been actively adding commits to 'pu', but we are in
pre-release freeze and I'll be tagging 1.6.6-rc2 hopefully later today.
Depending on how fast the earth rotates, perhaps I'll do so tomorrow, as I
am expecting one order-to-pull from the other side of the globe.
If anybody, including those who are working on new topics, notices a bug
that didn't exist in 1.6.5 in the post-1.6.5 code, please give it a higher
priority than anything else. Bugs and glitches that we had in 1.6.5 are
what users have lived with, and unless fixes to them are really trivial,
they can stay in the upcoming release a bit longer.
But new bugs introduced after 1.6.5, iow, regressions, are something we
would really want to avoid.
Thanks.
reply other threads:[~2009-12-09 21:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=7vws0vn78t.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--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