From: David Howells <dhowells@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: dhowells@redhat.com, linux-security-module@vger.kernel.org,
keyrings@linux-nfs.org, linux-arch@vger.kernel.org,
linux-api@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] Define ENONAMESERVICE and ENAMEUNKNOWN to indicate name service errors
Date: Tue, 08 Mar 2011 16:37:01 +0000 [thread overview]
Message-ID: <17429.1299602221@redhat.com> (raw)
In-Reply-To: <20110308152518.074d0996@lxorguk.ukuu.org.uk>
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> I was wondering if at least there was some co-ordination going on so that
> functions like perror() produced sensible answers. Otherwise it's
> debatable if its actually an improvement for the poor end user ?
Fair point. That's why I cc'd the messages to linux-api@, but I'm not sure who
actually reads it, besides Michael Kerrisk. I guess it's probably a good idea
to wave my suggestions on the glibc list at least.
David
next prev parent reply other threads:[~2011-03-08 16:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 15:02 [PATCH 1/2] Define ENOAUTHSERVICE to indicate "Authentication service unavailable" David Howells
2011-03-07 15:02 ` David Howells
[not found] ` <20110307150208.28218.89348.stgit-S6HVgzuS8uM4Awkfq6JHfwNdhmdF6hFW@public.gmane.org>
2011-03-07 15:02 ` [PATCH 2/2] Define ENONAMESERVICE and ENAMEUNKNOWN to indicate name service errors David Howells
2011-03-07 15:02 ` David Howells
[not found] ` <20110307150218.28218.84916.stgit-S6HVgzuS8uM4Awkfq6JHfwNdhmdF6hFW@public.gmane.org>
2011-03-07 16:00 ` Alan Cox
2011-03-07 16:00 ` Alan Cox
2011-03-08 15:09 ` David Howells
2011-03-08 15:25 ` Alan Cox
2011-03-08 16:37 ` David Howells [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-02-08 12:29 [PATCH 1/2] Define ENOAUTHSERVICE to indicate "Authentication service unavailable" David Howells
[not found] ` <20120208122905.8902.65762.stgit-S6HVgzuS8uM4Awkfq6JHfwNdhmdF6hFW@public.gmane.org>
2012-02-08 12:29 ` [PATCH 2/2] Define ENONAMESERVICE and ENAMEUNKNOWN to indicate name service errors David Howells
2012-02-08 12:29 ` David Howells
[not found] ` <20120208122917.8902.78395.stgit-S6HVgzuS8uM4Awkfq6JHfwNdhmdF6hFW@public.gmane.org>
2012-02-08 14:15 ` Jim Rees
2012-02-08 14:15 ` Jim Rees
2012-02-08 16:50 ` Steve French
[not found] ` <20120208141552.GA3273-63aXycvo3TyHXe+LvDLADg@public.gmane.org>
2012-02-09 10:04 ` David Howells
2012-02-09 10:04 ` David Howells
[not found] ` <17614.1328781889-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-02-09 13:44 ` Jim Rees
2012-02-09 13:44 ` Jim Rees
[not found] ` <20120209134429.GC6663-63aXycvo3TyHXe+LvDLADg@public.gmane.org>
2012-02-10 20:02 ` David Howells
2012-02-10 20:02 ` David Howells
2012-03-22 13:35 [PATCH 1/2] Define ENOAUTHSERVICE to indicate "Authentication service unavailable" David Howells
2012-03-22 13:35 ` [PATCH 2/2] Define ENONAMESERVICE and ENAMEUNKNOWN to indicate name service errors David Howells
2012-06-01 3:32 [PATCH 1/2] Define ENOAUTHSERVICE to indicate "Authentication service unavailable" Trond Myklebust
2012-06-01 3:32 ` [PATCH 2/2] Define ENONAMESERVICE and ENAMEUNKNOWN to indicate name service errors Trond Myklebust
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=17429.1299602221@redhat.com \
--to=dhowells@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=keyrings@linux-nfs.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.