From: u-igbb@aetey.se
To: musl@lists.openwall.com
Subject: Re: paths.h and similar constants, internal usage?
Date: Sat, 29 Mar 2014 17:36:09 +0000 [thread overview]
Message-ID: <20140329173609.GK8221@example.net> (raw)
In-Reply-To: <20140329171946.GV26358@brightrain.aerifal.cx>
Hello Rich,
On Sat, Mar 29, 2014 at 01:19:46PM -0400, Rich Felker wrote:
> paths.h is just there for making some bad legacy apps happy. It's not
> a system we want to use.
[... skipping the more detailed clarification ...]
Ok, I see you want to keep it separate (and possibly even be able
to lie to the legacy applications when you find it fit).
> Anyway, if you have specific requirements you're trying to find a
> solution to, please let us know what you're doing. For any request
> like this, a strong motivation is needed.
This was not a request, but mostly an offer. I felt that explicit
synchronization of identical strings might help consistency.
Not like I need this for my own purposes.
As to the contrary you want to keep these parts as far apart from each
other as possible, there is of course no sense in pursuing a non-goal. :)
Rune
prev parent reply other threads:[~2014-03-29 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-29 8:38 u-igbb
2014-03-29 17:19 ` Rich Felker
2014-03-29 17:36 ` u-igbb [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=20140329173609.GK8221@example.net \
--to=u-igbb@aetey.se \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).