public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Myers <bpm@sgi.com>
To: Hans-Peter Jansen <hpj@urpla.net>
Cc: xfs@oss.sgi.com
Subject: Re: Fwd: xfs_reno
Date: Thu, 7 Mar 2013 14:16:17 -0600	[thread overview]
Message-ID: <20130307201617.GT22182@sgi.com> (raw)
In-Reply-To: <20130307041348.GD6369@dastard>

Hi Pete,

On Thu, Mar 07, 2013 at 03:13:48PM +1100, Dave Chinner wrote:
> 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:
> 
> http://oss.sgi.com/archives/xfs/2007-11/msg00769.html
> 
> 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
> code.

Looks good to me as is.  Links and attribution are in the header, copyright
notices, etc.  We'll clean up that copyright header in the Makefile with a
separate commit authored by a current SGI employee.

You can add a Signed-off-by: Ben Myers <bpm@sgi.com> if you want.  No need to
repost just for that.

Thanks for spending the time!

Regards,
	Ben

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-03-07 20:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06 14:55 Fwd: xfs_reno Hans-Peter Jansen
2013-03-06 20:37 ` Eric Sandeen
2013-03-07  4:13 ` Dave Chinner
2013-03-07 20:16   ` Ben Myers [this message]
2013-03-11 21:48 ` Mark Tinguely
2013-03-12  9:02   ` Hans-Peter Jansen
2013-03-12 13:48     ` Mark Tinguely

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=20130307201617.GT22182@sgi.com \
    --to=bpm@sgi.com \
    --cc=hpj@urpla.net \
    --cc=xfs@oss.sgi.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