public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: fstests@vger.kernel.org
Subject: [PATCH 0/6] fstests: SPDX license conversion round 2
Date: Wed, 20 Jun 2018 12:04:11 +1000	[thread overview]
Message-ID: <20180620020417.14581-1-david@fromorbit.com> (raw)

Hi folks,

This is a smaller set of patches that convert the remaining GPLv2
license templates in the fstests tree to SPDX tags. The patches
should all be small enough to make it through to the list this time.

Mostly it was straight forward conversions with a little bit of
manual cleanup, but there's a couple of things we need clarification
on:

- src/log-writes has no copyright or license statements in either
  the code or in the upstream repository, so I haven't tagged it.

- src/perf has not copyright or license statements, but fstests is
  the upstream repository so I've tagged them as GPLv2.0

In both cases, we need Josef to add the correct copyrights and SPDX
tags to these files, and in future we should not accept code that
does not have either copyright or license statements in them.

There are some remaining files without tags. There are various
different reasons for that - not GPLv2, license statement didn't
match the scripts, no license statement to begin with, etc. These
will be addressed in a future patch set.

Comments?

-Dave.


             reply	other threads:[~2018-06-20  2:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-20  2:04 Dave Chinner [this message]
2018-06-20  2:04 ` [PATCH 1/6] dmapi: spdx license conversion Dave Chinner
2018-06-20  2:04 ` [PATCH 2/6] include/: " Dave Chinner
2018-06-20  2:04 ` [PATCH 3/6] lib/: " Dave Chinner
2018-06-20  2:04 ` [PATCH 4/6] src/aio-dio-regress/: " Dave Chinner
2018-06-20  2:04 ` [PATCH 5/6] src/: " Dave Chinner
2018-06-20  2:04 ` [PATCH 6/6] ltp/: " Dave Chinner
2018-06-21  1:55 ` [PATCH 0/6] fstests: SPDX license conversion round 2 Eryu Guan

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=20180620020417.14581-1-david@fromorbit.com \
    --to=david@fromorbit.com \
    --cc=fstests@vger.kernel.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