All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tziporet Koren <tziporet-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>
To: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Yevgeny Kliteynik
	<kliteyn-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>
Subject: Re: ibutils license problems + a few other minor issues
Date: Mon, 15 Feb 2010 22:50:28 +0200	[thread overview]
Message-ID: <4B79B394.50407@mellanox.co.il> (raw)
In-Reply-To: <4B743A4A.90004-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

On 2/11/2010 7:11 PM, Doug Ledford wrote:
> The ibutils tarball as found for download on the openfabrics web site
> has some licensing issues that need resolved ASAP.  The tarball in its
> current form is probably illegal to distribute until the items are
> fixed.  So, here's what popped up in review (done by Jay Fenlason):
>
> The COPYING files sprinkled around in the tarball are not consistent.
> Some of them contain a copy of the GPLv2, some of them contain a
> statement that the package is licensed under either GPLv2 in the file
> COPYING or the OFA BSD license included here in.  Of course, it doesn't
> work to reference a COPYING file from within the COPYING file you are
> referencing and say it has the information you aren't including here.  I
> would suggest that the proper place for the statement of GPLv2 or BSD is
> in possibly a LICENSE file with the COPYING file being the GPLv2 as
> stated.  It also seems redundant to have multiple COPYING files and
> possibly also multiple LICENSE files in a single tarball, so cleanup of
> unnecessary files seems in order here.
>    

Hi Doug
Thanks for providing the info (I  guess it was in this way from the 
first days we submitted the code to OFA)
Yevgeny will fix this soon

Tziporet
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2010-02-15 20:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-11 17:11 ibutils license problems + a few other minor issues Doug Ledford
     [not found] ` <4B743A4A.90004-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-02-15 20:50   ` Tziporet Koren [this message]
2010-02-23 17:01   ` Yevgeny Kliteynik

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=4B79B394.50407@mellanox.co.il \
    --to=tziporet-vpraknaxozvs1mouv/rt9w@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=kliteyn-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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.