linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Michael Opdenacker <michael.opdenacker@free-electrons.com>
Cc: trivial@kernel.org, lucas.demarchi@profusion.mobi,
	linux-doc@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	Jeff Garzik <jgarzik@pobox.com>
Subject: Re: [PATCH 2/2] [trivial] Documentation: broken URL in libata
Date: Mon, 13 Feb 2012 09:22:36 -0800	[thread overview]
Message-ID: <4F3946DC.3090102@xenotime.net> (raw)
In-Reply-To: <1329124192-27461-3-git-send-email-michael.opdenacker@free-electrons.com>

On 02/13/2012 01:09 AM, Michael Opdenacker wrote:
> Fix broken link to license text:
> http://www.opensource.org/licenses/osl-1.1.txt
> The text for version 1.1 of the Open Sofware license doesn't seem
> to be available anywhere on http://www.opensource.org/ any more.
> Replace it with a snapshot from the Internet Wayback Machine.

That's one option.
Too bad opensource.org doesn't provide archives.

OSL v1.1 is also available here:
http://fedoraproject.org/wiki/Licensing:OSL1.1

and here:
http://www.samurajdata.se/opensource/mirror/licenses/osl.php

Jeff, I don't suppose there is any chance of changing this file's license?
(since the Debian people found it to be a problem .. long ago)


> I first thought about hosting a copy of this file on my
> own website, but my website has less authority than
> an explicit backup of the original location.
> 
> Signed-off-by: Michael Opdenacker <michael.opdenacker@free-electrons.com>
> ---
>  Documentation/DocBook/libata.tmpl |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/DocBook/libata.tmpl b/Documentation/DocBook/libata.tmpl
> index cdd1bb9..bda33c1 100644
> --- a/Documentation/DocBook/libata.tmpl
> +++ b/Documentation/DocBook/libata.tmpl
> @@ -22,8 +22,8 @@
>     <para>
>     The contents of this file are subject to the Open
>     Software License version 1.1 that can be found at
> -   <ulink url="http://www.opensource.org/licenses/osl-1.1.txt">http://www.opensource.org/licenses/osl-1.1.txt</ulink> and is included herein
> -   by reference.
> +   <ulink url="http://web.archive.org/web/20060924133258/http://www.opensource.org/licenses/osl-1.1.txt">http://web.archive.org/web/20060924133258/http://www.opensource.org/licenses/osl-1.1.txt</ulink>
> +   and is included herein by reference.
>     </para>
>  
>     <para>


-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2012-02-13 17:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-13  9:09 [trivial] Documentation: fix broken URLs Michael Opdenacker
2012-02-13  9:09 ` [PATCH 1/2] [trivial] Documentation: broken URL in filesystems Michael Opdenacker
2012-02-13 17:19   ` Randy Dunlap
2012-02-13  9:09 ` [PATCH 2/2] [trivial] Documentation: broken URL in libata Michael Opdenacker
2012-02-13 17:22   ` Randy Dunlap [this message]
2012-09-13  4:18     ` Jeff Garzik

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=4F3946DC.3090102@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=jgarzik@pobox.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucas.demarchi@profusion.mobi \
    --cc=michael.opdenacker@free-electrons.com \
    --cc=trivial@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 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).