From: "Günther Noack" <gnoack@google.com>
To: "Konstantin Meskhidze (A)" <konstantin.meskhidze@huawei.com>
Cc: "Alejandro Colomar" <alx@kernel.org>,
"Mickaël Salaün" <mic@digikod.net>,
linux-man@vger.kernel.org, "Artem Kuzin" <artem.kuzin@huawei.com>
Subject: Re: [PATCH v3 2/2] landlock.7: Document Landlock ABI version 5 (IOCTL)
Date: Thu, 8 Aug 2024 12:09:10 +0200 [thread overview]
Message-ID: <ZrSZRi5BPelnaq6X@google.com> (raw)
In-Reply-To: <d06be80a-44ca-3eac-6b04-b5d2336309f0@huawei.com>
On Wed, Aug 07, 2024 at 03:09:02PM +0300, Konstantin Meskhidze (A) wrote:
> 7/31/2024 2:40 PM, Günther Noack пишет:
> > Konstantin: I would still appreciate if you could have a look and sign-off on
> > the networking documentation patch as well, since you are the original author of
> > much of that documentation on the kernel side.
>
> Hi Günther. I have checked the patch. It looks good, I left one question
> there. Please check it. Do I really need to sign-off it?
Thank you, Konstantin!
I would like to put both your "Co-developed-by" and "Signed-off-by" into the
patch, because:
(a) We should give you credit for the documentation that you've written :-),
and this man page change is based on your documentation in the kernel
Documentation/ directory and headers.
(b) Committing this man-page change would put it under the
"Linux-man-pages-copyleft" license, which is different than the licenses
used for the kernel, where the documentation was originally written. I
would like to add your "Co-developed-by" and "Signed-off-by", so that it's
clear that we all agree on this.
For reference, the rules for "Co-developed-by" are also discussed in [1].
Would that work for you, if we put your "Co-developed-by" and "Signed-off-by"
lines on the "ABI version 4" man page commit?
Thanks,
—Günther
[1] https://www.kernel.org/doc/html/latest/process/submitting-patches.html#when-to-use-acked-by-cc-and-co-developed-by
next prev parent reply other threads:[~2024-08-08 10:09 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 10:19 [PATCH v3 0/2] landlock*: Bring documentation up to date Günther Noack
2024-07-23 10:19 ` [PATCH v3 1/2] landlock.7, landlock_*.2: Document Landlock ABI version 4 Günther Noack
2024-07-23 13:03 ` Alejandro Colomar
2024-07-24 14:19 ` Günther Noack
2024-07-24 14:31 ` Alejandro Colomar
2024-07-24 14:51 ` Günther Noack
2024-07-24 14:54 ` Alejandro Colomar
2024-07-31 9:43 ` Günther Noack
2024-07-31 9:51 ` Alejandro Colomar
2024-08-06 8:38 ` Konstantin Meskhidze (A)
2024-08-06 10:19 ` Alejandro Colomar
2024-08-06 10:34 ` Konstantin Meskhidze (A)
2024-08-08 9:28 ` Günther Noack
2024-08-21 15:30 ` Konstantin Meskhidze (A)
2024-08-21 16:37 ` Günther Noack
2024-08-22 8:46 ` Konstantin Meskhidze (A)
2024-08-21 21:54 ` Alejandro Colomar
2024-08-22 8:47 ` Konstantin Meskhidze (A)
2024-07-23 10:19 ` [PATCH v3 2/2] landlock.7: Document Landlock ABI version 5 (IOCTL) Günther Noack
2024-07-31 10:58 ` Alejandro Colomar
2024-07-31 11:40 ` Günther Noack
2024-07-31 11:58 ` Alejandro Colomar
2024-08-07 12:09 ` Konstantin Meskhidze (A)
2024-08-08 10:09 ` Günther Noack [this message]
2024-08-16 12:37 ` Alejandro Colomar
2024-08-21 13:26 ` Konstantin Meskhidze (A)
2024-08-21 14:06 ` Alejandro Colomar
2024-08-21 15:24 ` Konstantin Meskhidze (A)
2024-08-21 13:30 ` Konstantin Meskhidze (A)
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=ZrSZRi5BPelnaq6X@google.com \
--to=gnoack@google.com \
--cc=alx@kernel.org \
--cc=artem.kuzin@huawei.com \
--cc=konstantin.meskhidze@huawei.com \
--cc=linux-man@vger.kernel.org \
--cc=mic@digikod.net \
/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.