From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, Jan Engelhardt <ej@inai.de>
Subject: Re: [libnftnl PATCH v2] Use SPDX License Identifiers in headers
Date: Wed, 30 Oct 2024 12:52:12 +0100 [thread overview]
Message-ID: <ZyId7EGcFpvVyDNc@orbyte.nwl.cc> (raw)
In-Reply-To: <ZyIX3MpPKPT2t_Zq@calendula>
On Wed, Oct 30, 2024 at 12:26:20PM +0100, Pablo Neira Ayuso wrote:
> On Tue, Oct 29, 2024 at 11:23:04PM +0100, Phil Sutter wrote:
> > Replace the copyright notice in header comments by an equivalent
> > SPDX-License-Identifier string as separate comment in line 1. Drop
> > resulting empty lines if duplicate or at the bottom of the comment.
> > Leave any other header comment content in place.
> >
> > This also fixes for an incomplete notice in examples/nft-ruleset-get.c
> > since commit c335442eefcca ("src: incorrect header refers to GPLv2
> > only").
> >
> > Signed-off-by: Phil Sutter <phil@nwl.cc>
>
> Reviewed-by Pablo Neira Ayuso <pablo@netfilter.org>
Patch applied.
prev parent reply other threads:[~2024-10-30 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 22:23 [libnftnl PATCH v2] Use SPDX License Identifiers in headers Phil Sutter
2024-10-30 11:26 ` Pablo Neira Ayuso
2024-10-30 11:52 ` Phil Sutter [this message]
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=ZyId7EGcFpvVyDNc@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=ej@inai.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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