public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <guaneryu@gmail.com>
To: Dave Chinner <david@fromorbit.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH 0/6] fstests: SPDX license conversion round 2
Date: Thu, 21 Jun 2018 09:55:37 +0800	[thread overview]
Message-ID: <20180621015537.GI2780@desktop> (raw)
In-Reply-To: <20180620020417.14581-1-david@fromorbit.com>

On Wed, Jun 20, 2018 at 12:04:11PM +1000, Dave Chinner wrote:
> 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.

Yeah, I'll pay more attentions to copyright statements. (I have a 'git
am' hook to make sure new tests have 'x' permission set, it shouldn't be
hard to extend the hook to check SPDX tags too. Or even further, write a
script like 'checkpatch.pl' in tools/ dir so everyone benefits from it).

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

Thanks a lot, Dave!

Eryu

> 
> Comments?
> 
> -Dave.
> 
> --
> To unsubscribe from this list: send the line "unsubscribe fstests" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2018-06-21  1:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-20  2:04 [PATCH 0/6] fstests: SPDX license conversion round 2 Dave Chinner
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 ` Eryu Guan [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=20180621015537.GI2780@desktop \
    --to=guaneryu@gmail.com \
    --cc=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