From: "H. Peter Anvin" <hpa@zytor.com>
To: Michael Kerrisk <mtk.manpages@gmail.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org
Subject: Re: [PATCH] dup2 w/flags
Date: Mon, 28 Apr 2008 13:54:33 -0700 [thread overview]
Message-ID: <48163989.2000405@zytor.com> (raw)
In-Reply-To: <517f3f820804280243q4a4bb9dbv27ce4be90fdd5954@mail.gmail.com>
Michael Kerrisk wrote:
>
> Ulrich,
>
> To repeat my earlier request, and as requested in Documentation/HOWTO,
> could you please CC me on API changes. This alerts me to what may
> eventually need documenting in man-pages.
>
I think we may need a mailing list for this; you're not the only person
who would be affected by ABI-visible changes.
-hpa
next prev parent reply other threads:[~2008-04-28 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 3:20 [PATCH] dup2 w/flags Ulrich Drepper
2008-04-28 9:43 ` Michael Kerrisk
2008-04-28 20:54 ` H. Peter Anvin [this message]
2008-04-28 21:00 ` Michael Kerrisk
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=48163989.2000405@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=torvalds@linux-foundation.org \
/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