From: Nicolas Pitre <nico@cam.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] Deltification library work by Nicolas Pitre.
Date: Thu, 19 May 2005 11:14:04 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.62.0505191104410.20274@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0505190736020.2322@ppc970.osdl.org>
On Thu, 19 May 2005, Linus Torvalds wrote:
> Sure. I'll apply this one and merge in Junio's rename on top of it, but I
> wanted to verify one thing first:
>
> > + * This file is free software; you can redistribute it and/or
> > + * modify it under the terms of the GNU Lesser General Public
> > + * License as published by the Free Software Foundation; either
> > + * version 2.1 of the License, or (at your option) any later version.
>
> I don't know the different LGPL versions, so can somebody verify that LGPL
> 2.1 is fully compatible with GPLv2...
>
> In fact I'd prefer to have that notice in the code to make it obvious that
> the LGPL becomes the GPLv2 when linked into the rest of git.
I don't mind switching it to GPL v2 if I'm allowed to. I kept LGPL v2.1
for that file since that's the license used for xdiff where significant
portion of that file has been copied from.
In fact I think the code in that file might be simplified even further
eventually, at which point there might not be much of the original code
left anymore and the license switched to GPL v2. But in the mean time
someone else with better knowledge of GPL vs LGPL interaction is needed
to give advice.
Nicolas
next prev parent reply other threads:[~2005-05-19 15:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 10:28 [PATCH] Deltification library work by Nicolas Pitre Junio C Hamano
2005-05-19 14:27 ` Nicolas Pitre
2005-05-19 14:38 ` Linus Torvalds
2005-05-19 15:14 ` Nicolas Pitre [this message]
2005-05-19 16:59 ` Junio C Hamano
2005-05-19 17:39 ` Nicolas Pitre
2005-05-19 15:36 ` Linus Torvalds
2005-05-19 15:40 ` Davide Libenzi
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=Pine.LNX.4.62.0505191104410.20274@localhost.localdomain \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=torvalds@osdl.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).