From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: One more 2.2-rc -- delaying the final
Date: Wed, 19 Nov 2014 13:31:13 -0800 [thread overview]
Message-ID: <xmqqoas2ri72.fsf@gitster.dls.corp.google.com> (raw)
As we have "oops, what was already added to 'master' is not quite
right" fixes for a few topics, I'd feel uneasy to release 2.2 final
without a -rc3. I was hoping that we can tag the final end of this
week, but let's make a -rc3 tomorrow or Friday and then do the final
one mid next week just before Turkey.
The ones I have in mind that I'd like to add for -rc3 are
- Christian's trailers fixes (two patches)
- David's "difftool --trust-exit-code" fix (one patch)
- Torsten's fix to test t5705 (one patch)
and smaller documentation fixes (which are not regression fixes).
Other things in 'next', even though many of them feel solid, are new
features that can wait for another cycle, I think.
Thanks.
reply other threads:[~2014-11-19 21:31 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=xmqqoas2ri72.fsf@gitster.dls.corp.google.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.