mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Richard Weinberger <richard@nod.at>
Cc: Kyle Moffett <kyle@moffetthome.net>,
	mfasheh@suse.com, jlbec@evilplan.org, ocfs2-devel@oss.oracle.com,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	license-violation@gpl-violations.org
Subject: Re: OCFS2 1.6.0 for mainline?
Date: Sat, 15 Oct 2011 17:25:35 -0400	[thread overview]
Message-ID: <37252.1318713935@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Sat, 15 Oct 2011 23:12:44 +0200." <4E99F74C.80900@nod.at>

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

On Sat, 15 Oct 2011 23:12:44 +0200, Richard Weinberger said:
> Am 15.10.2011 23:03, schrieb Kyle Moffett:
> > If someone who has a copy of Oracle's "Unbreakable Linux" can get
> > ahold of the sources, please put them in GIT somewhere for the rest of
> > us to access; it *is* GPLed software after all.  Otherwise, please
> > distribute the binaries to the rest of us and we will obtain the
> > sources on our own.  I can't find any published information on their
> > website about how to obtain the sources, so someone will have to
> > contact them directly.

Remember that Oracle only has an obligation to give source to the people *they*
give binaries to.  If you get binaries from an Oracle customer, you'll have to
hit that customer up for the corresponding source.

> I found this src.rpm:
> http://public-yum.oracle.com/repo/OracleLinux/OL6/1/base/x86_64/kernel-ue=
> k-2.6.32-100.34.1.el6uek.src.rpm
> 
> linux-2.6.32/fs/ocfs2 contains OCFS2 1.6.3.
> 
> Mark, Joel, can you please port this "release" to mainline?

I'll bite.. what's an acceptable Signed-Off-By: chain if somebody is pushing
somebody else's GPL'ed code upstream?  I seem to remember some maintainers
being a tad prickly about this case in the past?


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

  reply	other threads:[~2011-10-15 21:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-15 15:38 Richard Weinberger
2011-10-15 17:45 ` Valdis.Kletnieks
2011-10-15 17:49   ` Richard Weinberger
2011-10-15 19:26     ` Valdis.Kletnieks
2011-10-15 21:03       ` Kyle Moffett
2011-10-15 21:12         ` Richard Weinberger
2011-10-15 21:25           ` Valdis.Kletnieks [this message]
2011-10-17 17:16           ` Mark Fasheh
2011-11-09  7:55     ` Joel Becker
2011-11-09  9:47       ` Richard Weinberger
2011-10-15 17:50   ` Randy Dunlap
2011-10-16 14:20 Xose Vazquez Perez
2011-10-16 14:55 Xose Vazquez Perez
2011-10-16 17:40 ` Sasha Levin
2011-10-16 22:07   ` Xose Vazquez Perez
2011-10-16 22:44     ` richard -rw- weinberger
2011-10-16 23:24     ` Sasha Levin

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=37252.1318713935@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=jlbec@evilplan.org \
    --cc=kyle@moffetthome.net \
    --cc=license-violation@gpl-violations.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfasheh@suse.com \
    --cc=ocfs2-devel@oss.oracle.com \
    --cc=richard@nod.at \
    /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

all inboxes | Powered by JetHome®