All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: fstests@vger.kernel.org
Subject: [PATCH 0/9] fstests: Conversion of tests to SPDX license tags
Date: Sat,  9 Jun 2018 11:55:31 +1000	[thread overview]
Message-ID: <20180609015540.19385-1-david@fromorbit.com> (raw)

Hi folks,

I'm attempting to post this set of patches to the list now that
i've done the SPDX license tag conversion on Eryu's current
staging tree. I'm not sure it will all get through (it's a huge set
of patches), so after I've send this I'll push it all to a git tree
branch on kernel.org.

The conversion is described in detail in the commit message of the
first patch, so I won't repeat it here. It's all scripted, but
there's a few minor touchups that were needed to some files either
before or after the script was run due to non-standard formatting.

The patch is based on Eryu's staging tree, so the patches probably
won't apply to last week's released tree. fstests still appears to
run after the conversion, so I didn't completely break everything.

I'll follow up in the next couple of weeks with patches to convert
other remaining parts of fstests to use SPDX tags. That's a much
smaller job than converting all the tests, so I'll just send patches
for those conversions as I do them.

Cheers,

Dave.


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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-09  1:55 Dave Chinner [this message]
2018-06-09  1:55 ` [PATCH 1/9] fstests: Add LICENSES directory Dave Chinner
2018-06-09  1:55 ` [PATCH 2/9] common: convert to SPDX license tags Dave Chinner
2018-06-09  1:55 ` [PATCH 3/9] fstests: convert new test template to SPDX tags Dave Chinner
2018-06-09  1:55 ` [PATCH 8/9] fstests: convert top level files and tools to SPDX Dave Chinner
2018-06-09  1:55 ` [PATCH 9/9] fstests: make lsqa.pl work with SPDX tags Dave Chinner
2018-06-09  2:17 ` [PATCH 0/9] fstests: Conversion of tests to SPDX license tags Dave Chinner
2018-06-10 13:47   ` 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=20180609015540.19385-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.