From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] docs/manual: always point to the correct license file
Date: Sun, 10 Jun 2018 16:45:26 +0200 [thread overview]
Message-ID: <20180610164526.39af76ed@windsurf> (raw)
In-Reply-To: <20180602080101.23051-1-yann.morin.1998@free.fr>
Hello,
On Sat, 2 Jun 2018 10:01:01 +0200, Yann E. MORIN wrote:
> 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>
> ---
> docs/manual/manual.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
To be honest, I am not sure how likely it is that the COPYING file ever
changes. The copyright is owned by all the authors of the project, so a
license change would be very difficult to do.
But anyway, since the change was there and is pretty simple, I've
applied. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-06-10 14:45 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 [this message]
2018-06-10 15:04 ` Yann E. MORIN
2018-06-17 15:52 ` Peter Korsgaard
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=20180610164526.39af76ed@windsurf \
--to=thomas.petazzoni@bootlin.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 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.