[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <xmqq37kbspbu.fsf@gitster.mtv.corp.google.com>
Date: Tue, 04 Oct 2016 15:48:37 -0700
From: Junio C Hamano <gitster@...ox.com>
To: Rich Felker <dalias@...c.org>
Cc: James B <jamesbond3142@...il.com>, musl@...ts.openwall.com, Johannes Schindelin <Johannes.Schindelin@....de>, Jeff King <peff@...f.net>, git@...r.kernel.org
Subject: Re: Re: Regression: git no longer works with musl libc's regex impl
Rich Felker <dalias@...c.org> writes:
> This is especially unfriendly when the semantics of the switch come
> across, at least to some users, as "your system regex is incomplete"
> rather than "git can't use it because git depends on nonstandard
> extensions".
The latter is exactly what Makefile patch that brought this change
says, I think.
# Define NO_REGEX if your C library lacks regex support with REG_STARTEND
# feature.
Before the series updated the message to the above, we used to say:
# Define NO_REGEX if you have no or inferior regex support in your C library.
which _was_ unfair to those who needed to set NO_REGEX for whatever
reason. It was totally unclear "inferior" relative to what standard
the message was passing its harsh judgement on your C library.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
