public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "roland at gnu dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug ports/2172] [PATCH] move _PATH_LOG definition to <paths.h> (in sysdeps)
Date: Wed, 22 Feb 2006 02:46:00 -0000	[thread overview]
Message-ID: <20060222024652.28809.qmail@sourceware.org> (raw)
In-Reply-To: <20060118103705.2172.robertmh@gnu.org>


------- Additional Comments From roland at gnu dot org  2006-02-22 02:46 -------
I am not especially happy with the idea of pulling in all paths.h definitions
from syslog.h, and existing applications clearly require that _PATH_LOG be
defined in syslog.h.  I also haven't seen any other example of a system whose
paths.h does define _PATH_LOG, though putting it there is an obvious thing to do
and seems thoroughly harmless.  I am less sanguine about syslog.h pulling in
_PATH_*, which might annoy some existing source code.  The more conservative
patch would add a sysdeps files bits/syslog-path.h for it.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING


http://sourceware.org/bugzilla/show_bug.cgi?id=2172

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2006-02-22  2:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-18 10:37 [Bug ports/2172] New: " robertmh at gnu dot org
2006-01-18 10:38 ` [Bug ports/2172] " robertmh at gnu dot org
2006-02-22  2:46 ` roland at gnu dot org [this message]
2006-02-22 16:54 ` robertmh at gnu dot org
2006-02-23 22:50 ` cvs-commit at gcc dot gnu dot org
2007-02-18 13:58 ` aj at suse dot de

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=20060222024652.28809.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).