From: Roland McGrath <roland@hack.frob.com>
To: Zack Weinberg <zackw@panix.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: RFC: remove <sys/sysmacros.h> from <sys/types.h>
Date: Fri, 13 Nov 2015 23:43:00 -0000 [thread overview]
Message-ID: <20151113234333.D1DCA2C3B7B@topped-with-meat.com> (raw)
In-Reply-To: Zack Weinberg's message of Friday, 13 November 2015 09:21:46 -0500 <CAKCAbMiU=h2Vs3X-b8mRjP3Kig_TVngObPNpYauTqZs_=0q6Gg@mail.gmail.com>
Having <sys/types.h> define these macros is part of the original BSD API
that was the baseline for glibc long long ago. What do the modern BSDs
do about this issue?
next prev parent reply other threads:[~2015-11-13 23:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 14:21 Zack Weinberg
2015-11-13 14:29 ` Zack Weinberg
2015-11-13 14:45 ` Dmitry V. Levin
2015-11-13 15:59 ` Paul Eggert
2015-11-13 23:43 ` Roland McGrath [this message]
2015-11-14 9:18 ` Andreas Schwab
2015-11-14 20:41 ` Zack Weinberg
2015-11-14 21:59 ` Rich Felker
2015-11-14 22:19 ` Andreas Schwab
2015-11-21 0:19 ` Roland McGrath
2015-11-21 0:56 ` Zack Weinberg
2015-11-14 20:19 ` Carlos O'Donell
2015-11-19 4:13 ` RFC: deprecate sys/sysmacros.h inclusion from sys/types.h Zack Weinberg
2015-12-07 14:03 ` Zack Weinberg
2015-12-21 20:31 ` Zack Weinberg
2016-01-11 15:16 ` Zack Weinberg
2016-01-11 15:27 ` Carlos O'Donell
2016-01-11 18:02 ` Zack Weinberg
2016-01-11 20:50 ` Carlos O'Donell
2015-12-29 20:42 ` Mike Frysinger
2015-12-29 21:56 ` Zack Weinberg
2015-12-29 22:45 ` Mike Frysinger
2016-02-19 20:56 ` Mike Frysinger
2016-04-20 17:37 ` Mike Frysinger
2016-04-20 17:58 ` Zack Weinberg
2016-04-20 18:11 ` Mike Frysinger
2016-04-21 19:31 ` Roland McGrath
2016-04-21 21:00 ` Zack Weinberg
2016-04-21 21:11 ` Roland McGrath
2017-10-21 12:10 RFC: remove <sys/sysmacros.h> from <sys/types.h> Andreas K. Huettel
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=20151113234333.D1DCA2C3B7B@topped-with-meat.com \
--to=roland@hack.frob.com \
--cc=libc-alpha@sourceware.org \
--cc=zackw@panix.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).