From: Stephen Hemminger <stephen@networkplumber.org>
To: David Marchand <david.marchand@redhat.com>
Cc: Paul Szczepanek <paul.szczepanek@arm.com>,
Patrick Robb <probb@iol.unh.edu>,
dev@dpdk.org, thomas@monjalon.net, techboard@dpdk.org
Subject: Re: [PATCH] devtools: enhance the license check
Date: Wed, 11 Dec 2024 06:55:54 -0800 [thread overview]
Message-ID: <20241211065554.25c3757c@hermes.local> (raw)
In-Reply-To: <CAJFAV8zpnZXoHTye5RpmJaRn3RETXAbC47NoXHO8XKcDCsVm5A@mail.gmail.com>
On Wed, 11 Dec 2024 10:00:38 +0100
David Marchand <david.marchand@redhat.com> wrote:
> On Tue, Dec 10, 2024 at 6:00 PM Stephen Hemminger
> <stephen@networkplumber.org> wrote:
> >
> > On Tue, 10 Dec 2024 10:10:39 +0100
> > David Marchand <david.marchand@redhat.com> wrote:
> >
> > > +no_license_list=\
> > > +':^.git* :^.mailmap :^.ci/* :^README :^MAINTAINERS :^VERSION :^ABI_VERSION :^*/Kbuild '\
> > > +':^*/README* :^license/ :^config/ :^buildtools/ :^*/poetry.lock '\
> > > +':^kernel/linux/uapi/.gitignore :^kernel/linux/uapi/version :^*.cocci :^*.abignore '\
> > > +':^*.map :^*.ini :^*.data :^*.json :^*.cfg :^*.txt :^*.svg :^*.png'
> > > +
> >
> > What is poetry.lock?
>
> I don't know.
> It looks like some python packaging config for dts, and it is a generated file.
> # This file is automatically @generated by Poetry 1.8.3 and should not
> be changed by hand.
>
> Cc: dts maintainers.
>
>
Put it in .gitignore then please, and the script will ignore that.
next prev parent reply other threads:[~2024-12-11 14:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 9:10 [PATCH] devtools: enhance the license check David Marchand
2024-12-10 17:00 ` Stephen Hemminger
2024-12-11 9:00 ` David Marchand
2024-12-11 14:55 ` Stephen Hemminger [this message]
2024-12-11 15:01 ` Thomas Monjalon
2024-12-11 21:22 ` Patrick Robb
2024-12-13 15:51 ` David Marchand
2025-03-14 13:55 ` Thomas Monjalon
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=20241211065554.25c3757c@hermes.local \
--to=stephen@networkplumber.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=paul.szczepanek@arm.com \
--cc=probb@iol.unh.edu \
--cc=techboard@dpdk.org \
--cc=thomas@monjalon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).