From: "Seebs" <seebs@seebs.net>
To: "Mark Hatle" <mark.hatle@kernel.crashing.org>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/2] pseudo: Fix statx function usage
Date: Mon, 12 Oct 2020 14:21:37 -0500 [thread overview]
Message-ID: <20201012142137.72207395@seebsdell> (raw)
In-Reply-To: <a2369d3c-ed7e-b03b-8538-aefe09008288@kernel.crashing.org>
On Mon, 12 Oct 2020 14:14:36 -0500
"Mark Hatle" <mark.hatle@kernel.crashing.org> wrote:
> I looked into this. It appears (after pseudo was written, but) about
> 7 or so years ago, all of the man pages were re-written and the
> language was changed.
I don't think I originally intentionally synchronized it with man
pages, I just had the convention of special-casing "path", and then
started using "pathname" as a convention for "a name that holds a
path but we don't want to do the magic on it".
-s
next prev parent reply other threads:[~2020-10-12 19:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 16:20 [PATCH 1/2] pseudo: do not expand symlinks in /proc Richard Purdie
2020-10-07 16:20 ` [PATCH 2/2] pseudo: Fix statx function usage Richard Purdie
2020-10-12 19:08 ` [OE-core] " Seebs
2020-10-12 19:14 ` Mark Hatle
2020-10-12 19:21 ` Seebs [this message]
2020-10-12 20:25 ` Richard Purdie
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=20201012142137.72207395@seebsdell \
--to=seebs@seebs.net \
--cc=mark.hatle@kernel.crashing.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.