From: Salvatore Bonaccorso <carnil@debian.org>
To: AsciiWolf <mail@asciiwolf.com>
Cc: Michal Kubecek <mkubecek@suse.cz>,
Petter Reinholdtsen <pere@debian.org>,
netdev@vger.kernel.org, Robert Scheck <fedora@robert-scheck.de>
Subject: Re: [mail@asciiwolf.com: Re: ethtool: Incorrect component type in AppStream metainfo causes issues and possible breakages]
Date: Wed, 30 Apr 2025 17:02:53 +0200 [thread overview]
Message-ID: <aBI7nWLq32_mHMRT@eldamar.lan> (raw)
In-Reply-To: <CAB-mu-QfzzZX8x-rPsras9r7jA2vMSpNqimV0h-OBOaa-z2tuQ@mail.gmail.com>
Hi,
On Wed, Apr 30, 2025 at 04:46:28PM +0200, AsciiWolf wrote:
> GPL is not a valid AppStream metadata license. See the official spec:
> https://freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-metadata_license
Yes, you are right, so nothing to change here.
Regards,
Salvatore
prev parent reply other threads:[~2025-04-30 15:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 13:47 [mail@asciiwolf.com: Re: ethtool: Incorrect component type in AppStream metainfo causes issues and possible breakages] Michal Kubecek
[not found] ` <CAB-mu-QjxGvBHGzaVmwBpq-0UXALzdSpzcvVQPvyXjFAnxZkqA@mail.gmail.com>
2025-04-11 14:07 ` ethtool: Incorrect component type in AppStream metainfo causes issues and possible breakages Petter Reinholdtsen
2025-04-11 20:18 ` [mail@asciiwolf.com: Re: ethtool: Incorrect component type in AppStream metainfo causes issues and possible breakages] AsciiWolf
2025-04-11 20:48 ` AsciiWolf
2025-04-24 13:29 ` Salvatore Bonaccorso
2025-04-25 16:46 ` Michal Kubecek
2025-04-25 19:38 ` Salvatore Bonaccorso
2025-04-29 20:37 ` Michal Kubecek
2025-04-30 14:43 ` Salvatore Bonaccorso
[not found] ` <CAB-mu-QfzzZX8x-rPsras9r7jA2vMSpNqimV0h-OBOaa-z2tuQ@mail.gmail.com>
2025-04-30 15:02 ` Salvatore Bonaccorso [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=aBI7nWLq32_mHMRT@eldamar.lan \
--to=carnil@debian.org \
--cc=fedora@robert-scheck.de \
--cc=mail@asciiwolf.com \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=pere@debian.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;
as well as URLs for NNTP newsgroup(s).