qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Chetan <chetan4windows@gmail.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH] Fixing LGPL version number
Date: Thu, 8 Oct 2020 14:52:30 +0530	[thread overview]
Message-ID: <CAPPKfOE2bOYjCPQSqAfOnvqfYhY1d5hJE-1MqO1VsuQ8qqwgCQ@mail.gmail.com> (raw)
In-Reply-To: <1c24b564-9870-10f9-ac37-c4ebfacc74f0@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 3966 bytes --]

On Thu, Oct 8, 2020 at 2:18 PM Thomas Huth <thuth@redhat.com> wrote:
>I'm also not sure whether it's legally possible to replace the license text
>without agreement of all authors of the file ... so better don't do a
global
>patch for that right now, start with one subsystem instead and see whether
>it gets accepted... or maybe we should only add the SPDX tags, without
>removing the license text? ... this all might require some more discussions
>first ...

I'll put those changes on hold then, for now.

On Thu, Oct 8, 2020 at 2:34 PM Thomas Huth <thuth@redhat.com> wrote:
>Phew, that's a pretty huge patch, could you maybe split it by subsystem /
>folder so that it is easier to review?

Sorry about that. Sure, I'll split the patch in different versions folder
wise.

>I'm not sure whether we should update the version in the files that just
say
>"LGPL" (and do not mention "Lesser") ... they could also refer to the GNU
>*Library* GPL instead, which was available as version 2 (in the sense of
2.0).
>Could you please drop the hunks for the files that only mention LGPL for
now?

Ok. I'll exclude the files which mention just LGPL in the revision.

Chetan.

On Thu, Oct 8, 2020 at 2:34 PM Thomas Huth <thuth@redhat.com> wrote:

> On 08/10/2020 08.05, Chetan Pant wrote:
> > There is no "version 2" of the "Lesser" General Public License. It is
> > either "GPL version 2.0" or "LGPL version 2.1". This patch replaces all
> > occurrences of "LGPL version 2" with "LGPL version 2.1" in comment
> section.
> >
> > Signed-off-by: Chetan Pant <chetan4windows@gmail.com>
>
> Phew, that's a pretty huge patch, could you maybe split it by subsystem /
> folder so that it is easier to review?
>
> [...]
> > diff --git a/net/hub.h b/net/hub.h
> > index ce45f7b..83e33e4 100644
> > --- a/net/hub.h
> > +++ b/net/hub.h
> > @@ -7,7 +7,7 @@
> >   *  Stefan Hajnoczi   <stefanha@linux.vnet.ibm.com>
> >   *  Zhi Yong Wu       <wuzhy@linux.vnet.ibm.com>
> >   *
> > - * This work is licensed under the terms of the GNU LGPL, version 2 or
> later.
> > + * This work is licensed under the terms of the GNU LGPL, version 2.1
> or later.
> >   * See the COPYING.LIB file in the top-level directory.
> >   *
> >   */
>
> I'm not sure whether we should update the version in the files that just
> say
> "LGPL" (and do not mention "Lesser") ... they could also refer to the GNU
> *Library* GPL instead, which was available as version 2 (in the sense of
> 2.0).
> Could you please drop the hunks for the files that only mention LGPL for
> now?
>
> > diff --git a/target/i386/hvf/x86_emu.c b/target/i386/hvf/x86_emu.c
> > index d3e289e..da570e3 100644
> > --- a/target/i386/hvf/x86_emu.c
> > +++ b/target/i386/hvf/x86_emu.c
> > @@ -5,7 +5,7 @@
> >   * This program 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 of the License, or (at your option) any later version.
> > + * version 2.1 of the License, or (at your option) any later version.
> >   *
> >   * This program is distributed in the hope that it will be useful,
> >   * but WITHOUT ANY WARRANTY; without even the implied warranty of
> > @@ -23,7 +23,7 @@
> >  //  This library 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 of the License, or (at your option) any later version.
> > +//  version 2.1 of the License, or (at your option) any later version.
> >  //
> >  //  This library is distributed in the hope that it will be useful,
> >  //  but WITHOUT ANY WARRANTY; without even the implied warranty of
>
> That's an interesting file - the license text shows up twice here... I
> wonder whether we could scratch one of the two... but that's also something
> for a separate patch, I think.
>
>  Thomas
>
>

[-- Attachment #2: Type: text/html, Size: 5430 bytes --]

      reply	other threads:[~2020-10-08  9:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-08  6:05 [PATCH] Fixing LGPL version number Chetan Pant
2020-10-08  6:13 ` no-reply
2020-10-08  7:54 ` Philippe Mathieu-Daudé
2020-10-08  7:57   ` Thomas Huth
2020-10-08  8:40     ` Chetan
2020-10-08  8:48       ` Thomas Huth
2020-10-08 10:22       ` Daniel P. Berrangé
2020-10-08 10:55         ` Chetan
2020-10-08  9:04 ` Thomas Huth
2020-10-08  9:22   ` Chetan [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=CAPPKfOE2bOYjCPQSqAfOnvqfYhY1d5hJE-1MqO1VsuQ8qqwgCQ@mail.gmail.com \
    --to=chetan4windows@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=thuth@redhat.com \
    /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).