From: Alejandro Colomar <alx.manpages@gmail.com>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 4/4] fts.3: tfix
Date: Tue, 5 Jul 2022 00:02:22 +0200 [thread overview]
Message-ID: <ba2e454e-3dec-e877-9b51-d02a9f5ae747@gmail.com> (raw)
In-Reply-To: <f05a70b218089c288c3cefd1b2fbb4650a119eed.1656887003.git.nabijaczleweli@nabijaczleweli.xyz>
[-- Attachment #1.1: Type: text/plain, Size: 1078 bytes --]
Hi,
On 7/4/22 00:23, наб wrote:
> statp -> fts_statp
>
> Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
I tried to apply this patch, but it doesn't want to. I guess it depends
on previous patches in this set, so I'll wait for v2.
Cheers,
Alex
> ---
> man3/fts.3 | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/man3/fts.3 b/man3/fts.3
> index 627bb5afc..601a74cd5 100644
> --- a/man3/fts.3
> +++ b/man3/fts.3
> @@ -433,7 +433,7 @@ pathnames were provided as arguments to
> By default, returned
> .I FTSENT
> structures reference file characteristic information (the
> -.I statp
> +.I fts_statp
> field) for each file visited.
> This option relaxes that requirement as a performance optimization,
> allowing the
> @@ -442,7 +442,7 @@ fts functions to set the
> field to
> .B FTS_NSOK
> and leave the contents of the
> -.I statp
> +.I fts_statp
> field undefined.
> .TP
> .B FTS_SEEDOT
--
Alejandro Colomar
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-07-04 22:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 22:23 [PATCH 1/4] fts.3: note that lstat(2) may also provide fts_statp наб
2022-07-03 22:23 ` [PATCH 2/4] fts.3: list primary modes first, remove triplicate requirement spiel наб
2022-07-04 21:57 ` Alejandro Colomar
2022-07-03 22:23 ` [PATCH 3/4] fts.3: wfix наб
2022-07-04 21:59 ` Alejandro Colomar
2022-07-03 22:23 ` [PATCH 4/4] fts.3: tfix наб
2022-07-04 22:02 ` Alejandro Colomar [this message]
2022-07-03 23:04 ` [PATCH 1/4] fts.3: note that lstat(2) may also provide fts_statp Alejandro Colomar
2022-07-03 23:12 ` наб
2022-07-03 23:32 ` Alejandro Colomar
2022-07-04 21:53 ` Alejandro Colomar
2022-07-05 16:21 ` [PATCH v2 1/5] " наб
2022-07-05 17:23 ` Alejandro Colomar
2022-07-05 16:21 ` [PATCH v2 2/5] fts.3: remove triplicate requirement spiel наб
2022-07-05 16:21 ` [PATCH v2 3/5] fts.3: clarify FTS_COMFOLLOW behaviour наб
2022-07-05 16:22 ` [PATCH v2 4/5] fts.3: list primary modes first наб
2022-07-05 16:22 ` [PATCH v2 5/5] fts.3: tfix наб
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=ba2e454e-3dec-e877-9b51-d02a9f5ae747@gmail.com \
--to=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=nabijaczleweli@nabijaczleweli.xyz \
/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