[Top] [All Lists]

Re: Fwd: xfs_reno

To: Hans-Peter Jansen <hpj@xxxxxxxxx>
Subject: Re: Fwd: xfs_reno
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Thu, 7 Mar 2013 15:13:48 +1100
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20351675.Zy117sIl8Z@xrated>
References: <20351675.Zy117sIl8Z@xrated>
User-agent: Mutt/1.5.21 (2010-09-15)
On Wed, Mar 06, 2013 at 03:55:19PM +0100, Hans-Peter Jansen wrote:
> Hi Dave,
> I tried to gather Barrys SOB, but failed so far. His trace ends in 2009 
> google 
> wise.
> How is this case usually handled?
> Here's the current state of things.

He was working for SGI at the time, so you should be able to get
anyone from SGI provide a valid S-O-B if needed.

As it is, I can probably verify the patch origins sufficiently
to add a SOB to it as:


It's pretty clear that the code was released under the GPL and free
from any tainted code by SGI. The post I'm pointing to above is one
I made while an SGI employee, and it effectively verifies the origin
of the code in the same way a S-O-B does.

So, you probably don't even need to chase a S-O-B from SGI if you
just point at that email and attribute the code correctly. i.e.
retaining al the SGI copyright notices in the code and saying inteh
patch description that the code was originally authored by SGI and
released under the same license as the rest of the xfs userspace


Dave Chinner

<Prev in Thread] Current Thread [Next in Thread>