mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Roland Hieber <rohieb@rohieb.name>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <rohieb@rohieb.name>
Subject: [ptxdist] [PATCH] doc: dev_manual: two URL fixes
Date: Sat,  6 Jul 2019 15:31:15 +0200	[thread overview]
Message-ID: <20190706133115.13990-1-rohieb@rohieb.name> (raw)

The gnu.org URL never showed SPDX identifiers, replace it by a link to
the official license list.

The licenses-list repository has been renamed and restructured.

Signed-off-by: Roland Hieber <rohieb@rohieb.name>
---
 doc/dev_manual.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/dev_manual.rst b/doc/dev_manual.rst
index dfadcb241..cd1d2e9fc 100644
--- a/doc/dev_manual.rst
+++ b/doc/dev_manual.rst
@@ -763,7 +763,7 @@ SPDX License Identifiers
 
 A list of SPDX license identifiers can be found here:
 
-   https://www.gnu.org/licenses/license-list.html#SoftwareLicenses
+   https://spdx.org/licenses/
 
 Help to Detect the Correct License
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -772,7 +772,7 @@ License identification isn't trivial. A help in doing so can be the following
 repository and its content. It contains a list of known licenses based on their
 SPDX identifier. The content is without formatting to simplify text search.
 
-   https://github.com/spdx/license-list.git
+   https://github.com/spdx/license-list-data/tree/master/text
 
 Advanced Rule Files
 ~~~~~~~~~~~~~~~~~~~
-- 
2.20.1


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

                 reply	other threads:[~2019-07-06 13:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20190706133115.13990-1-rohieb@rohieb.name \
    --to=rohieb@rohieb.name \
    --cc=ptxdist@pengutronix.de \
    /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