Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] docs/manual: always point to the correct license file
Date: Sun, 17 Jun 2018 17:52:42 +0200	[thread overview]
Message-ID: <877emxpfzp.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180602080101.23051-1-yann.morin.1998@free.fr> (Yann E. MORIN's message of "Sat, 2 Jun 2018 10:01:01 +0200")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

 > The manual is GPL-2, and points to the COPYING file in the repository.
 > When we do a rendering of the manual for a specific version, that URL
 > is currently always poitning to the latest version of the COPYING file.

 > If we ever have to change the content of that file (e.g. to add a new
 > exception, more clarifications, a license change, or whatever), then
 > an old manual would point to that newer version, which would then be
 > incorrect.

 > Include the sha1 of the commit in the URL, so that the manual always
 > point to the tree at the time the manual was rendered, not the time
 > it is consulted. Contrary to the informative text above, use the full
 > sha1, not the shortened one.

 > Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
 > Cc: Thomas De Schampheleire <patrickdepinguin@gmail.com>
 > Cc: Luca Ceresoli <luca@lucaceresoli.net>

Committed to 2018.02.x, thanks.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2018-06-17 15:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-02  8:01 [Buildroot] [PATCH] docs/manual: always point to the correct license file Yann E. MORIN
2018-06-10 14:45 ` Thomas Petazzoni
2018-06-10 15:04   ` Yann E. MORIN
2018-06-17 15:52 ` Peter Korsgaard [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=877emxpfzp.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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