From: Alejandro Colomar <alx.manpages@gmail.com>
To: Quentin Monnet <quentin@isovalent.com>
Cc: Rumen Telbizov <rumen.telbizov@menlosecurity.com>,
linux-man <linux-man@vger.kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: Update bpf-helpers(7) man page
Date: Wed, 20 Jul 2022 23:47:27 +0200 [thread overview]
Message-ID: <7d125b8d-9873-b001-dae2-a78d3891f144@gmail.com> (raw)
In-Reply-To: <CACdoK4KuoRpTdyLqtPTbctHWHtfQTNgZoKunVC_f7T_y4ATF5g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1051 bytes --]
Hi Quentin,
On 7/20/22 23:44, Quentin Monnet wrote:
> Since you're offering, I wouldn't mind leaving it to you to run the
> script before each release. I'm willing to help, but I don't really
> trust myself with remembering this every time, so having it written
> down as one of the steps in your RELEASE file is probably the best way
> to make sure the update happens.
Yep.
>
> Please do reach out if the script didn't behave as expected, though.
> I'll be happy to assist.
Okay, I'll try it and will come back if I need help.
Thanks!
>
>> but if something changes in that script, it would be nice to notify us,
>> if we're using them.
>
> I do realise we failed to send a notice when we renamed the script,
> please accept my apologies for that. I'll be more careful in the
> future.
I wasn't yet involved in maintaining the man-pages at the time the
script changed, so no need to apologize to me :p
Cheers,
Alex
>
> Thanks,
> Quentin
--
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 21:47 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
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 [this message]
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=7d125b8d-9873-b001-dae2-a78d3891f144@gmail.com \
--to=alx.manpages@gmail.com \
--cc=daniel@iogearbox.net \
--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