From: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: Ulrich Drepper <drepper-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org,
linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org
Subject: Re: [PATCH] cleanup paccept
Date: Tue, 28 Oct 2008 15:15:31 -0400 [thread overview]
Message-ID: <20081028191531.GA1007@infradead.org> (raw)
In-Reply-To: <200810281909.m9SJ9pdj003624-sQhldQRnEDHy+ZiRM8QlFPXAX3CI6PSWQQ4Iyu8u01E@public.gmane.org>
On Tue, Oct 28, 2008 at 03:09:51PM -0400, Ulrich Drepper wrote:
> This patch doesn't change *any* functionality from what is currently
> in the upstream kernel. There is no reason to start arguing again and
> for me to explain everything the way I did it months ago. This is just
> a *cleanup patch*, nothing else. If you want to know why this cleanup
> is needed read the discussions of
Umm, it does enabled functionality that wasn't enabled before. And that
functionality includes a syscall. So any chance you could write a
proper changelog that describes what you actually do instead of lots of
ranting and references to old posts?
And no "[PATCH] cleanup paccept" isn't really a good subject for adding
a new syscalls either.
--
To unsubscribe from this list: send the line "unsubscribe linux-api" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-10-28 19:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 19:09 [PATCH] cleanup paccept Ulrich Drepper
[not found] ` <200810281909.m9SJ9pdj003624-sQhldQRnEDHy+ZiRM8QlFPXAX3CI6PSWQQ4Iyu8u01E@public.gmane.org>
2008-10-28 19:15 ` Christoph Hellwig [this message]
2008-10-28 19:17 ` Linus Torvalds
2008-10-28 20:10 ` Michael Kerrisk
[not found] ` <517f3f820810281310y2b02705fs8b402a5ca5117f51-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-10-28 20:20 ` 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=20081028191531.GA1007@infradead.org \
--to=hch-wegcikhe2lqwvfeawa7xhq@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=drepper-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.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;
as well as URLs for NNTP newsgroup(s).