From: Askar Safin <safinaskar@zohomail.com>
To: dhowells@redhat.com
Cc: christian.brauner@ubuntu.com, linux-api@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-man@vger.kernel.org, viro@zeniv.linux.org.uk
Subject: Re: [PATCH 1/5] Add manpage for open_tree(2)
Date: Sat, 1 Feb 2025 05:43:22 +0300 [thread overview]
Message-ID: <20250201024322.2625842-1-safinaskar@zohomail.com> (raw)
In-Reply-To: <159680892602.29015.6551860260436544999.stgit@warthog.procyon.org.uk>
David Howells, ping! You still didn't add all these manpages.
https://lore.kernel.org/linux-man/159680892602.29015.6551860260436544999.stgit@warthog.procyon.org.uk/
next prev parent reply other threads:[~2025-02-01 2:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 14:02 [PATCH 1/5] Add manpage for open_tree(2) David Howells
2020-08-07 14:02 ` [PATCH 2/5] Add manpages for move_mount(2) and open_tree(2) David Howells
2020-08-22 20:04 ` Michael Kerrisk (man-pages)
2020-08-24 10:08 ` David Howells
2020-08-26 7:31 ` Michael Kerrisk (man-pages)
2020-08-07 14:02 ` [PATCH 3/5] Add manpage for fspick(2) David Howells
2020-08-22 20:05 ` Michael Kerrisk (man-pages)
2020-08-07 14:02 ` [PATCH 4/5] Add manpage for fsopen(2) and fsmount(2) David Howells
2020-08-22 20:08 ` Michael Kerrisk (man-pages)
2020-08-07 14:02 ` [PATCH 5/5] Add manpage for fsconfig(2) David Howells
2020-08-07 15:58 ` AW: " Walter Harms
2020-08-07 16:27 ` David Howells
2020-08-07 16:35 ` AW: " Walter Harms
2020-08-22 20:18 ` Michael Kerrisk (man-pages)
2020-08-22 20:01 ` [PATCH 1/5] Add manpage for open_tree(2) Michael Kerrisk (man-pages)
2025-02-01 2:43 ` Askar Safin [this message]
2025-08-05 16:45 ` Aleksa Sarai
-- strict thread matches above, loose matches on Subject: below --
2020-08-24 12:24 David Howells
2020-08-27 11:01 ` Michael Kerrisk (man-pages)
2021-01-22 8:39 ` Michael Kerrisk (man-pages)
2021-08-13 0:20 ` Michael Kerrisk (man-pages)
2021-02-25 19:03 ` Aurélien Aptel
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=20250201024322.2625842-1-safinaskar@zohomail.com \
--to=safinaskar@zohomail.com \
--cc=christian.brauner@ubuntu.com \
--cc=dhowells@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).