patches and low-level development discussion
 help / color / mirror / code / Atom feed
From: Alyssa Ross <hi@alyssa.is>
To: Cole Helbling <cole.e.helbling@outlook.com>
Cc: devel@spectrum-os.org
Subject: Re: [PATCH mktuntap v2] Become REUSE 3.0 compliant
Date: Fri, 31 Jul 2020 11:20:26 +0000	[thread overview]
Message-ID: <873658dj7p.fsf@alyssa.is> (raw)
In-Reply-To: <SJ0PR03MB55813F06854B271E968797AEB3720@SJ0PR03MB5581.namprd03.prod.outlook.com>

"Cole Helbling" <cole.e.helbling@outlook.com> writes:

> On Sun Jul 26, 2020 at 4:01 AM PDT, Alyssa Ross wrote:
>> See <https://reuse.software/>. NLnet are quite keen on this.
>> ---
>> v1 accidentally included some unrelated changes.
>>
>> .editorconfig | 3 +
>> .gitignore | 5 +-
>> COPYING | 339 ----------------------------------
>> LICENSES/CC0-1.0.txt | 119 ++++++++++++
>> LICENSES/GPL-2.0-only.txt | 319 ++++++++++++++++++++++++++++++++
>> LICENSES/GPL-2.0-or-later.txt | 319 ++++++++++++++++++++++++++++++++
>> Makefile | 16 +-
>> README | 6 +
>> TODO | 3 +
>> mktuntap.8 | 16 +-
>> mktuntap.c | 16 +-
>> 11 files changed, 776 insertions(+), 385 deletions(-)
>> delete mode 100644 COPYING
>> create mode 100644 LICENSES/CC0-1.0.txt
>> create mode 100644 LICENSES/GPL-2.0-only.txt
>> create mode 100644 LICENSES/GPL-2.0-or-later.txt
>
> Not much to say other than LGTM. Again, REUSE looks interesting.
>
> Glad you caught the extraneous changes in v1 before I had a chance to
> call you out. :P
>
> Reviewed-by: Cole Helbling <cole.e.helbling@outlook.com>

Thanks, applied. :)

To ssh://atuin/home/spectrum/git/mktuntap.git
   234261e..c4d29c5  master -> master

      reply	other threads:[~2020-07-31 11:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-26 10:45 [PATCH mktuntap] " Alyssa Ross
2020-07-26 11:01 ` [PATCH mktuntap v2] " Alyssa Ross
2020-07-27 18:46   ` Cole Helbling
2020-07-31 11:20     ` Alyssa Ross [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=873658dj7p.fsf@alyssa.is \
    --to=hi@alyssa.is \
    --cc=cole.e.helbling@outlook.com \
    --cc=devel@spectrum-os.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.
Code repositories for project(s) associated with this public inbox

	https://spectrum-os.org/git/crosvm
	https://spectrum-os.org/git/doc
	https://spectrum-os.org/git/mktuntap
	https://spectrum-os.org/git/nixpkgs
	https://spectrum-os.org/git/spectrum
	https://spectrum-os.org/git/ucspi-vsock
	https://spectrum-os.org/git/www

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).