From: Alejandro Colomar <alx.manpages@gmail.com>
To: Rumen Telbizov <rumen.telbizov@menlosecurity.com>
Cc: linux-man@vger.kernel.org, quentin@isovalent.com
Subject: Re: Update bpf-helpers(7) man page
Date: Wed, 20 Jul 2022 11:50:05 +0200 [thread overview]
Message-ID: <6310b542-3a92-e072-b369-25e370036626@gmail.com> (raw)
In-Reply-To: <CA+FoirA75vZgYaDdNfJGUwR6sVCYZ6YL4T3mN_LNPpzeJ5pYhg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 800 bytes --]
Hi Rumen,
On 7/19/22 19:21, Rumen Telbizov wrote:
> Hi Alejandro,
>
> Thanks for following up on this.
> Quentin will send you the script these days for you to rerun.
> However, I'm wondering if there's a way to run it automatically when a change is
> detected or otherwise without needing manual intervention? This way
> the published
> page will not get out of date. I am not sure what that mechanism might be but
> just a thought.
I'm not sure an automated mechanism would be easy to set up.
But, I'm planning to add a RELEASE file to the man-pages repo with
instructions to make a release. I can add there a step that reminds to
refresh the bpf-helpers(7) manual page before every release.
Cheers,
Alex
--
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-20 9:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 16:37 Update bpf-helpers(7) man page Rumen Telbizov
2022-07-19 14:42 ` Alejandro Colomar
2022-07-19 17:21 ` Rumen Telbizov
2022-07-20 9:50 ` Alejandro Colomar [this message]
2022-07-20 20:40 ` Quentin Monnet
2022-07-20 21:06 ` Alejandro Colomar
2022-07-20 21:44 ` Quentin Monnet
2022-07-20 21:47 ` Alejandro Colomar
2022-07-20 22:44 ` Rumen Telbizov
2022-07-21 11:27 ` Alejandro Colomar
2022-07-21 18:16 ` Rumen Telbizov
2022-08-24 16:02 ` Jakub Wilk
2022-08-24 16:48 ` Quentin Monnet
2022-08-24 22:07 ` Quentin Monnet
2022-08-24 22:51 ` Alejandro Colomar
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=6310b542-3a92-e072-b369-25e370036626@gmail.com \
--to=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=quentin@isovalent.com \
--cc=rumen.telbizov@menlosecurity.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox