From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Andrew Rodland <andrew@cleverdomain.org>, git@vger.kernel.org
Subject: Re: USE_NSEC bug?
Date: Wed, 20 Mar 2013 15:00:53 -0400 [thread overview]
Message-ID: <20130320190053.GC30165@sigill.intra.peff.net> (raw)
In-Reply-To: <7vobedewer.fsf@alter.siamese.dyndns.org>
On Wed, Mar 20, 2013 at 11:52:28AM -0700, Junio C Hamano wrote:
> Jeff King <peff@peff.net> writes:
>
> > So I think your real complaint is "configure does not set NO_NSEC
> > properly", which is something worth fixing.
>
> Yes.
>
> I think our "Meh" was about "do we want to unify USE_NSEC and
> NO_NSEC?" and nothing else.
Exactly. Now I am hoping Andrew will volunteer to fix configure.ac, as I
will be happy to go to my grave never having had to figure out autoconf
m4 syntax ever again. :)
-Peff
prev parent reply other threads:[~2013-03-20 19:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 6:36 USE_NSEC bug? Andrew Rodland
2013-03-20 7:53 ` Jeff King
2013-03-20 17:04 ` Junio C Hamano
2013-03-20 17:09 ` Jeff King
2013-03-20 17:31 ` Junio C Hamano
2013-03-20 18:22 ` Andrew Rodland
2013-03-20 18:30 ` Jeff King
2013-03-20 18:52 ` Junio C Hamano
2013-03-20 19:00 ` Jeff King [this message]
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=20130320190053.GC30165@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=andrew@cleverdomain.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).