public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: James.Bottomley@SteelEye.com
Cc: linux-scsi@vger.kernel.org
Subject: Re: GFDL issue in Documentation/DocBook/scsidrivers.tmpl
Date: Mon, 25 Aug 2003 14:43:26 +0200	[thread overview]
Message-ID: <20030825124326.GA15940@lst.de> (raw)
In-Reply-To: <3F378408.9090708@torque.net>

On Mon, Aug 11, 2003 at 09:54:48PM +1000, Douglas Gilbert wrote:
> Christoph Hellwig wrote:
> >As discussed in the thread at
> >http://www.ussg.iu.edu/hypermail/linux/kernel/0306.1/1928.html
> >we agreed that GFDL is not an acceptable license for documentation
> >in the kernel tree, but file in subject still comes under that
> >license.
> >
> >Douglas, any chance you could relicense it under something
> >GPL-compatible?  It probably wants folding into scsi_mid_low_api.txt
> >anyway..
> 
> Is the attached preferable?
> [Switch GFDL to GPL]

James, could you apply this patch?

> 
> 
> Doug Gilbert
> 

> --- linux/Documentation/DocBook/scsidrivers.tmpl	2003-01-09 22:09:24.000000000 +1000
> +++ linux/Documentation/DocBook/scsidrivers.tmpl260t3gpl	2003-08-11 08:50:09.000000000 +1000
> @@ -16,20 +16,40 @@
>      </affiliation>
>     </author>
>    </authorgroup>
> -  <pubdate>2002-04-27</pubdate>
> +  <pubdate>2003-08-11</pubdate>
>  
>    <copyright>
>     <year>2002</year>
> +   <year>2003</year>
>     <holder>Douglas Gilbert</holder>
>    </copyright>
> +
>    <legalnotice>
>     <para>
> -    Permission is granted to copy, distribute and/or modify this
> -    document under the terms of the GNU Free Documentation License,
> -    Version 1.1 or any later version published by the Free Software
> -    Foundation; with no Invariant Sections, with no Front-Cover Texts,
> -    and with no Back-Cover Texts.  A copy of the license is included
> -    in the section entitled "GNU Free Documentation License".
> +     This documentation is free software; you can redistribute
> +     it and/or modify it under the terms of the GNU General Public
> +     License as published by the Free Software Foundation; either
> +     version 2 of the License, or (at your option) any later
> +     version.
> +   </para>
> +      
> +   <para>
> +     This program is distributed in the hope that it will be
> +     useful, but WITHOUT ANY WARRANTY; without even the implied
> +     warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> +     See the GNU General Public License for more details.
> +   </para>
> +      
> +   <para>
> +     You should have received a copy of the GNU General Public
> +     License along with this program; if not, write to the Free
> +     Software Foundation, Inc., 59 Temple Place, Suite 330, Boston,
> +     MA 02111-1307 USA
> +   </para>
> +      
> +   <para>
> +     For more details see the file COPYING in the source
> +     distribution of Linux.
>     </para>
>    </legalnotice>
>  

---end quoted text---

      parent reply	other threads:[~2003-08-25 12:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-07 16:25 GFDL issue in Documentation/DocBook/scsidrivers.tmpl Christoph Hellwig
2003-08-11 11:54 ` Douglas Gilbert
2003-08-11 11:56   ` Christoph Hellwig
2003-08-25 12:43   ` Christoph Hellwig [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=20030825124326.GA15940@lst.de \
    --to=hch@lst.de \
    --cc=James.Bottomley@SteelEye.com \
    --cc=linux-scsi@vger.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