All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
	Mark Kettenis <kettenis@openbsd.org>
Subject: Re: [PATCH v2] errno.3: ENODATA is an XSI STREAMS extension
Date: Sat, 20 Mar 2021 20:31:36 +0100	[thread overview]
Message-ID: <0dc5409f-dff9-cbf7-e522-e5c25df75577@gmail.com> (raw)
In-Reply-To: <8735wp1w3i.fsf@mid.deneb.enyo.de>

Hi Florian,

On 3/20/21 8:08 PM, Florian Weimer wrote:
> 
> Would it make sense to mention that this error code is reused for
> extended attributes?
> 

Hmm, I think so.  In fact, AFAICS in the man-pages, it is only used for
that:

[
$ grep -rn ENODATA man?
man2/setxattr.2:124:.B ENODATA
man2/setxattr.2:129:.\" .BR ENODATA
man2/getxattr.2:118:.B ENODATA
man2/getxattr.2:123:.\" .BR ENODATA
man2/removexattr.2:85:.B ENODATA
man2/removexattr.2:89:.\" .BR ENODATA
man3/errno.3:405:.B ENODATA
]

Proposal:

[
       ENODATA
              The  named  attribute does not exist, or the process
              has no access to this attribute.

              In POSIX.1-2001 (XSI STREAMS option), this error was
              described as  "No message is available on the STREAM
              head read queue".

]

What do you think about it?

Thanks,

Alex


-- 
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

  reply	other threads:[~2021-03-20 19:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-19 23:57 [PATCH] errno.3: ENODATA is an XSI STREAMS extension Alejandro Colomar
2021-03-20  9:58 ` Jakub Wilk
2021-03-20 11:41   ` Alejandro Colomar (man-pages)
2021-03-20 11:42     ` [PATCH v2] " Alejandro Colomar
2021-03-20 19:08       ` Florian Weimer
2021-03-20 19:31         ` Alejandro Colomar (man-pages) [this message]
2021-03-20 19:41           ` Florian Weimer
2021-03-20 20:01             ` [PATCH v3] errno.3: Fix ENODATA text Alejandro Colomar
2021-04-04 20:16               ` Michael Kerrisk (man-pages)
2021-04-04 20:17                 ` Michael Kerrisk (man-pages)

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=0dc5409f-dff9-cbf7-e522-e5c25df75577@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=fw@deneb.enyo.de \
    --cc=kettenis@openbsd.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.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 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.