All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe MacDonald <Joe_MacDonald@mentor.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Martin Jansa <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-networking][PATCH] iftop: 1.0pre2 -> 1.0pre4
Date: Wed, 16 Sep 2015 09:38:53 -0400	[thread overview]
Message-ID: <20150916133853.GC10507@mentor.com> (raw)
In-Reply-To: <46D89522-87AA-48C1-9B6C-5408B26BA3BB@gmail.com>

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

[Re: [oe] [meta-networking][PATCH] iftop: 1.0pre2 -> 1.0pre4] On 15.09.15 (Tue 13:17) Khem Raj wrote:

> 
> > On Sep 15, 2015, at 10:24 AM, Joe MacDonald <Joe_MacDonald@mentor.com> wrote:
> > 
> > [Re: [oe] [meta-networking][PATCH] iftop: 1.0pre2 -> 1.0pre4] On 15.09.15 (Tue 09:52) Khem Raj wrote:
> > 
> >> On Tue, Sep 15, 2015 at 1:52 AM, Kang Kai <Kai.Kang@windriver.com> wrote:
> >>> Got it.
> >>> 
> >>> For for iftop, it just update licensing text.
> >>> 
> >>> ----------------------------
> >>> revision 1.3
> >>> date: 2014/01/01 14:50:05;  author: pdw;  state: Exp;  lines: +7 -8
> >>> Update to licensing text.  Patch by Robert Scheck <robert@fedoraproject.org>
> >>> ----------------------------
> >>> 
> >> 
> >> what was updated in essence is important here not logs
> > 
> > Yeah, I had hoped that would've come through in either the earlier link
> > or my referencing it here.  I inspected the change myself and the
> > changes are limited to replacing 'library' with 'lesser' and the street
> > address of the FSF in the GPL text, which isn't surprising, but that's
> > really the information that should have been communicated in the commit
> > log itself.
> 
> ‘library' GPL ( LGPL ) and ‘Lesser' GPL ( LGPL ) are they same ? I think we need to find more

I don't remember exactly when it happened but I know it was a general
shift in the FSF to change the language for LGPL to mean "lesser" rather
than "library" in the early 2000s.  The thinking at the time was that
"library" implied the license would only apply to shared libraries due
to the wording, when really the intent was to be more BSD-ish.

In this case, though, the question isn't relevant because the change to
the license is actually the GPLv2 one which contains a reference to LGPL
by name (formerly library but now lesser).  The current text in Kai's
update is the text that comes from the FSF website when you look at the
GPLv2 license.  The package and the license is GPLv2, though, not LGPL,
so the semantics of that change don't matter.

In general I agree that Kai's commit log (and subsequent follow-up)
aren't sufficient at all, but I was feeling bad about all of the
back-and-forth with Wind River's China office lately and thought I'd go
the extra distance to do his research for him and merge the patch if
possible.

-J.

> 
> > 
> > -- 
> > -Joe MacDonald.
> > :wq
> 

-- 
-Joe MacDonald.
:wq

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 484 bytes --]

      reply	other threads:[~2015-09-16 13:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-10  5:38 [meta-networking][PATCH] iftop: 1.0pre2 -> 1.0pre4 kai.kang
2015-09-14 19:37 ` Joe MacDonald
2015-09-15  8:52   ` Kang Kai
2015-09-15 16:52     ` Khem Raj
2015-09-15 17:24       ` Joe MacDonald
2015-09-15 20:17         ` Khem Raj
2015-09-16 13:38           ` Joe MacDonald [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=20150916133853.GC10507@mentor.com \
    --to=joe_macdonald@mentor.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.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 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.