All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Jann Horn <jannh@google.com>,
	Michael Kerrisk-manpages <mtk.manpages@gmail.com>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: open_tree() manpage submission fell through the cracks?
Date: Mon, 4 May 2020 14:43:34 +0200	[thread overview]
Message-ID: <20200504124334.GA19904@dell5510> (raw)
In-Reply-To: <CAG48ez3xjhUDd3qMm=cEa+asLvrQOXEpVs4_w6Y6MuerymMbCg@mail.gmail.com>

Hi Jann,

> I noticed that open_tree() doesn't have a manpage yet; and while
> looking for a WIP manpage on the lists, I found this mail, which is
> from February, submits manpages for open_tree() and other related
> syscalls, and doesn't seem to have a response from you:

> https://lore.kernel.org/linux-fsdevel/20200207174236.18882-1-pvorel@suse.cz/

> I wonder whether maybe you haven't seen that mail in the first place.
> It was addressed to linux-man@vger.kernel.org as "To" and
> mtk.manpages@gmail.com as "Cc", which is the reverse of what's
> suggested at <https://www.kernel.org/doc/man-pages/patches.html>...
> maybe that runs into some filter on your side? Or maybe it just landed
> in a spam filter somewhere or something like that?

Thanks for pointing out this patchset and also preferred way to send patches.

I'd also appreciate these new syscalls were documented, thus
I've pinged Michael some time ago and got his reply:
https://lore.kernel.org/linux-man/9655825c-be5d-3941-60da-ccb8e5e433cb@gmail.com/

He's probably just too busy.

Kind regards,
Petr

  reply	other threads:[~2020-05-04 12:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-04 11:17 open_tree() manpage submission fell through the cracks? Jann Horn
2020-05-04 12:43 ` Petr Vorel [this message]
2020-05-11 15:13 ` 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=20200504124334.GA19904@dell5510 \
    --to=pvorel@suse.cz \
    --cc=jannh@google.com \
    --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.