[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 14 Aug 2013 17:28:32 +0200
From: Luca Barbato <lu_zero@...too.org>
To: musl@...ts.openwall.com
Subject: Re: Build system adjustments for subarchs
On 14/08/13 17:15, Rich Felker wrote:
> Indeed, I figured this out too from reading GNU make's changelog. The
> documentation should really document any feature that hasn't been
> supported for at least 10 years with a note about which version/year
> it was added in, so users can make informed decisions about which
> features to depend on, and the examples in the documentation should
> refrain from using the new, incompatible syntax for something that has
> a more compatible variant. It's really unexpected to find examples
> depending on extremely new features in the manual when the adjacent
> pages are talking about gcc 1.3 as if it were current...
gnumake (as bash) lacks proper release policies so I wouldn't expect to
have a non-misleading documentation.
lu
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.
