From: ogawa.yasufumi@lab.ntt.co.jp
To: spp@dpdk.org, ferruh.yigit@intel.com, ogawa.yasufumi@lab.ntt.co.jp
Cc: tim.odriscoll@intel.com, jim.st.leger@intel.com,
tdelanerolle@linuxfoundation.org
Subject: [spp] [PATCH 0/9] Change license of docs to SPDX
Date: Fri, 19 Oct 2018 16:05:25 +0900 [thread overview]
Message-ID: <20181019070534.81134-1-ogawa.yasufumi@lab.ntt.co.jp> (raw)
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Hi,
It is still remained old license description in docs because I did not
update while source codes are changed to SPDX tag.
This series of patches is for updating license descriptions of the
remaining docs.
I cc'ed Tim, Jim and Trishan because this update is related to license.
Regards,
Yasufumi
Yasufumi Ogawa (9):
docs: convert license of commands to SPDX tag
docs: convert license of overview to SPDX tag
docs: convert license of setup guides to SPDX tag
docs: convert license of tools to SPDX tag
docs: convert license of spp_vf commands to SPDX
docs: convert license of spp_vf usecases to SPDX
docs: convert license of spp_vf gsg to SPDX
docs: convert license of spp_vf expl to SPDX
docs: convert license of spp_vf to SPDX
docs/guides/commands/common.rst | 32 ++---------------------------
docs/guides/commands/experimental.rst | 31 +---------------------------
docs/guides/commands/index.rst | 33 ++----------------------------
docs/guides/commands/primary.rst | 32 ++---------------------------
docs/guides/commands/secondary.rst | 31 ++--------------------------
docs/guides/index.rst | 31 ++--------------------------
docs/guides/overview.rst | 31 ++--------------------------
docs/guides/setup/getting_started.rst | 34 +++----------------------------
docs/guides/setup/howto_use.rst | 32 ++---------------------------
docs/guides/setup/index.rst | 31 ++--------------------------
docs/guides/setup/performance_opt.rst | 32 ++---------------------------
docs/guides/setup/use_cases.rst | 31 ++--------------------------
docs/guides/spp_vf/commands/common.rst | 31 ++--------------------------
docs/guides/spp_vf/commands/index.rst | 31 ++--------------------------
docs/guides/spp_vf/commands/primary.rst | 32 ++---------------------------
docs/guides/spp_vf/commands/secondary.rst | 31 ++--------------------------
docs/guides/spp_vf/design.rst | 31 ++--------------------------
docs/guides/spp_vf/explain/functions.rst | 31 ++--------------------------
docs/guides/spp_vf/explain/index.rst | 31 ++--------------------------
docs/guides/spp_vf/gsg/build.rst | 31 ++--------------------------
docs/guides/spp_vf/gsg/howto_use.rst | 31 ++--------------------------
docs/guides/spp_vf/gsg/index.rst | 31 ++--------------------------
docs/guides/spp_vf/index.rst | 31 ++--------------------------
docs/guides/spp_vf/overview.rst | 31 ++--------------------------
docs/guides/spp_vf/use_cases/index.rst | 31 ++--------------------------
docs/guides/spp_vf/use_cases/usecase1.rst | 31 ++--------------------------
docs/guides/tools/index.rst | 31 ++--------------------------
27 files changed, 54 insertions(+), 793 deletions(-)
--
2.13.1
next reply other threads:[~2018-10-19 7:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 7:05 ogawa.yasufumi [this message]
2018-10-19 7:05 ` [spp] [PATCH 1/9] docs: convert license of commands to SPDX tag ogawa.yasufumi
2018-10-19 7:05 ` [spp] [PATCH 2/9] docs: convert license of overview " ogawa.yasufumi
2018-10-19 7:05 ` [spp] [PATCH 3/9] docs: convert license of setup guides " ogawa.yasufumi
2018-10-19 7:05 ` [spp] [PATCH 4/9] docs: convert license of tools " ogawa.yasufumi
2018-10-19 7:05 ` [spp] [PATCH 5/9] docs: convert license of spp_vf commands to SPDX ogawa.yasufumi
2018-10-19 7:05 ` [spp] [PATCH 6/9] docs: convert license of spp_vf usecases " ogawa.yasufumi
2018-10-19 7:05 ` [spp] [PATCH 7/9] docs: convert license of spp_vf gsg " ogawa.yasufumi
2018-10-19 7:05 ` [spp] [PATCH 8/9] docs: convert license of spp_vf expl " ogawa.yasufumi
2018-10-19 7:05 ` [spp] [PATCH 9/9] docs: convert license of spp_vf " ogawa.yasufumi
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=20181019070534.81134-1-ogawa.yasufumi@lab.ntt.co.jp \
--to=ogawa.yasufumi@lab.ntt.co.jp \
--cc=ferruh.yigit@intel.com \
--cc=jim.st.leger@intel.com \
--cc=spp@dpdk.org \
--cc=tdelanerolle@linuxfoundation.org \
--cc=tim.odriscoll@intel.com \
/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).