git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: RFD: should we do another 2.3-rc for t9001-noxmailer? I'd say not
Date: Sun, 01 Feb 2015 14:48:00 -0800	[thread overview]
Message-ID: <xmqqr3u98d0f.fsf@gitster.dls.corp.google.com> (raw)

I was reviewing the recent bugs and fixes for the last time, and was
wondering if we want to do 2.3-rc3 with build fix for those with
ancient cURL (tc/curl-vernum-output-broken-in-7.11) and workaround
for those with Perl with older Getopt::Long (tc/t9001-noxmailer).

 - The former is not a regression between 2.2 and 2.3 (i.e. 2.2
   already had the same use of curl-config output).

 - The latter, strictly speaking, is a regression in that tests used
   to pass but tests in 2.3 no longer pass for those with older
   Getopt::Long.

But the latter is about a test script that lacks work-around, and
more importantly, everybody has lived with unconditional X-mailer:
output, and the minority with ancient Getopt::Long will survive
without being to able to give the new --no-xmailer (or --noxmailer)
option just fine.

So currently I am leaning to keep these two fixes where they are and
tag 2.3 final without them in a few days.

             reply	other threads:[~2015-02-01 22:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-01 22:48 Junio C Hamano [this message]
2015-02-02  9:29 ` RFD: should we do another 2.3-rc for t9001-noxmailer? I'd say not Tom G. Christensen
2015-02-02 20:38 ` Jeff King
2015-02-02 20:52   ` Junio C Hamano

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=xmqqr3u98d0f.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 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).