From: ScrelliCopter <ScrelliCopter@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: pcem-17
Date: Sun, 28 Mar 2021 18:42:09 +0200 [thread overview]
Message-ID: <20210328164209.PFPNzvAVsPLsoQStBTbw2gzDMdGDXtLvJJ3YL0y-OmY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29285@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
New comment by ScrelliCopter on void-packages repository
https://github.com/void-linux/void-packages/pull/29285#issuecomment-808922315
Comment:
Author of the first PR here, just saw this.
In my experience Void usually puts precedence on the first PR in the case of duplicates. I'm not precious about who gets to be maintainer but if you'd like to make sure any improvements over my template (touché on using create_wrksrc) make it in I'd be happy to take reviews on my PR.
It seems you already figured out the reasons behind everything I was doing but I'll elaborate on why I chose `GPL-2.0-or-later`:
Sarah never appeared to have included a copy of the GPL or attached any GPL text to her own code, grepping thru showed a lot of "version 2 (or at your option) any later version"; and actually I just looked thru v17 again and `src/f82c710_upc.c` and `src/sound_azt2316a.c` are version **3** or later, so it seems like the license field should actually be `GPL-3.0-or-later` 🤷.
next prev parent reply other threads:[~2021-03-28 16:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 0:43 [PR PATCH] " ajshell1
2021-03-07 0:44 ` [PR PATCH] [Updated] " ajshell1
2021-03-07 3:19 ` ajshell1
2021-03-13 16:07 ` ajshell1
2021-03-13 17:25 ` ajshell1
2021-03-13 17:38 ` [PR REVIEW] " ajshell1
2021-03-13 17:55 ` [PR PATCH] [Updated] " ajshell1
2021-03-13 18:05 ` ajshell1
2021-03-28 16:42 ` ScrelliCopter [this message]
2021-11-06 23:12 ` abenson
2021-11-06 23:12 ` [PR PATCH] [Closed]: " abenson
-- strict thread matches above, loose matches on Subject: below --
2020-05-27 2:11 [PR PATCH] New package: pcem-16 ScrelliCopter
2021-11-06 23:12 ` New package: pcem-17 abenson
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=20210328164209.PFPNzvAVsPLsoQStBTbw2gzDMdGDXtLvJJ3YL0y-OmY@z \
--to=screllicopter@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).