All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Lehmann <pcg@schmorp.de>
To: Arjan van de Ven <arjanv@redhat.com>, linux-kernel@vger.kernel.org
Cc: Cameron Patrick <cameron@patrick.wattle.id.au>,
	Michael Frank <mhf@linuxmail.org>, Pavel Machek <pavel@suse.cz>,
	Software Suspend - Mailing Lists 
	<swsusp-devel@lists.sourceforge.net>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [Swsusp-devel] lzf license
Date: Thu, 25 Mar 2004 16:02:24 +0100	[thread overview]
Message-ID: <20040325150224.GC11633@schmorp.de> (raw)
In-Reply-To: <20040323114725.GD13666@devserv.devel.redhat.com>

On Tue, Mar 23, 2004 at 12:47:26PM +0100, Arjan van de Ven <arjanv@redhat.com> wrote:
> About bugfixes; I'd recommend using something like:

That sounds reasonable. Sorry for the delay, but I didn't receive your
mail earlier (not being on the cc:).

I have added this notice to all core files of the distribution and
released it as 1.3, assuming that this solves all the problems. It can
temporarily be found here: http://data.plan9.de/liblzf-1.3.tar.gz

The files in the kernel diverge a tiny bit (being a slight subset), and I
think it's easiest to just add the additional notice to the files:

   kernel/power/lzf/lzf_c.c
   kernel/power/lzf/lzf_d.c

The following should be applied to both files:

diff -u -p
@@ -24,6 +24,16 @@
  * WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTH-
  * ERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
  * OF THE POSSIBILITY OF SUCH DAMAGE.
+ *
+ * Alternatively, the contents of this file may be used under the terms of
+ * the GNU General Public License version 2 (the "GPL"), in which case the
+ * provisions of the GPL are applicable instead of the above. If you wish to
+ * allow the use of your version of this file only under the terms of the
+ * GPL and not to allow others to use your version of this file under the
+ * BSD license, indicate your decision by deleting the provisions above and
+ * replace them with the notice and other provisions required by the GPL. If
+ * you do not delete the provisions above, a recipient may use your version
+ * of this file under either the BSD or the GPL.
  */



-- 
      -----==-                                             |
      ----==-- _                                           |
      ---==---(_)__  __ ____  __       Marc Lehmann      +--
      --==---/ / _ \/ // /\ \/ /       pcg@goof.com      |e|
      -=====/_/_//_/\_,_/ /_/\_\       XX11-RIPE         --+
    The choice of a GNU generation                       |
                                                         |

  reply	other threads:[~2004-03-25 15:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-22  9:18 Michael Frank
2004-03-22  9:40 ` [Swsusp-devel] (no subject) Cameron Patrick
2004-03-22  9:49   ` Arjan van de Ven
2004-03-22 10:02     ` LZF inclusion in kernel Michael Frank
2004-03-22 18:21     ` [Swsusp-devel] lzf license Marc Lehmann
2004-03-23 11:47       ` Arjan van de Ven
2004-03-25 15:02         ` Marc Lehmann [this message]
2004-03-24 22:20       ` Nigel Cunningham
2004-03-25 14:26         ` Marc Lehmann
2004-03-25 14:56           ` Pavel Machek
2004-03-28  0:43             ` Marc Lehmann
2004-03-22 10:15   ` [Swsusp-devel] (no subject) Pavel Machek
2004-03-25 15:18 ` Marc Lehmann

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=20040325150224.GC11633@schmorp.de \
    --to=pcg@schmorp.de \
    --cc=arjanv@redhat.com \
    --cc=cameron@patrick.wattle.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhf@linuxmail.org \
    --cc=pavel@suse.cz \
    --cc=swsusp-devel@lists.sourceforge.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.