From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: linux-man@vger.kernel.org, Alejandro Colomar <alx@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Boqun Feng <boqun.feng@gmail.com>, paulmck <paulmck@kernel.org>
Subject: rseq(2) man page
Date: Fri, 6 Jan 2023 12:16:03 -0500 [thread overview]
Message-ID: <095c479b-baed-9d11-08a1-e698f59763d9@efficios.com> (raw)
Hi!
I would like to contribute a man page for the rseq(2) system call to the
man-pages project. I maintain this system call which appeared in Linux 4.18.
I have done several attempts to contribute a man page for it in the past,
so let's hope we will have more luck this time.
I have just done some improvements to the man page, here is its current
location:
https://git.kernel.org/pub/scm/libs/librseq/librseq.git/tree/doc/man/rseq.2
Please let me know if this is a good time to contribute it, and if I need
to do significant changes before submitting again.
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
next reply other threads:[~2023-01-06 17:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 17:16 Mathieu Desnoyers [this message]
2023-01-06 17:22 ` rseq(2) man page Alejandro Colomar
2023-01-06 17:50 ` Alejandro Colomar
2023-01-06 20:57 ` Mathieu Desnoyers
2023-01-06 22:57 ` Alejandro Colomar
2023-01-10 16:54 ` Mathieu Desnoyers
2023-01-10 19:28 ` Alejandro Colomar
2023-01-10 19:57 ` Mathieu Desnoyers
2023-01-10 19:03 ` man page width limit and example indentation (was: rseq(2) man page) G. Branden Robinson
2023-01-10 20:29 ` Alejandro Colomar
2023-01-10 21:39 ` G. Branden Robinson
2023-01-10 23:30 ` Alejandro Colomar
2023-01-11 15:31 ` G. Branden Robinson
2023-01-11 15:39 ` G. Branden Robinson
2023-01-06 18:49 ` rseq(2) man page Mathieu Desnoyers
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=095c479b-baed-9d11-08a1-e698f59763d9@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=alx@kernel.org \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox