xfs
[Top] [All Lists]

Re: Question on how to submit changed code

To: Roger Willcocks <roger@xxxxxxxxxxxxxxxx>
Subject: Re: Question on how to submit changed code
From: Carlos Maiolino <cmaiolino@xxxxxxxxxx>
Date: Tue, 1 Dec 2015 18:44:37 +0100
Cc: "Epp, Mike" <MEpp@xxxxxxxxxxxxxxxx>, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <1448991660.16687.159.camel@xxxxxxxxxxxxxxxxxxxxxxxx>
Mail-followup-to: Roger Willcocks <roger@xxxxxxxxxxxxxxxx>, "Epp, Mike" <MEpp@xxxxxxxxxxxxxxxx>, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>
References: <105716A9A63E8A4C9CB26A0F29E203DCF40BE069@usbpx2pmxmbx12> <1448991660.16687.159.camel@xxxxxxxxxxxxxxxxxxxxxxxx>
User-agent: Mutt/1.5.24 (2015-08-30)
On Tue, Dec 01, 2015 at 05:41:00PM +0000, Roger Willcocks wrote:
> 
> On Tue, 2015-12-01 at 15:16 +0000, Epp, Mike wrote:
> > I have changed code in libxfs and repair projects for xfsprogs.  I
> > donât view the changes as desired for ongoing deployment, as they
> > allowed scanning of active volumes and bring the chance of false
> > errors.  To stay compliant with GNU GPL though we must publish the
> > code.  What are the steps I need to follow to publish the changes?  Do
> > I need to publish just the source files I changed, the entire projects
> > I changes, or all of xfsprogs?
> > 
> 
> You don't need to publish the code but you do need to make a full copy
> of the code, including your clearly marked changes, available to your
> customers.
> 
> See GPL section 3.

Just FYI, xfsprogs is licensed under GPL V2, not V3, they are different in many
aspects.

> 
> >  
> > 
> > Mike Epp, Senior Software Engineer
> > 
> > Kroll Ontrack |  9023 Columbine Road, Eden Prairie, MN 55347
> > mepp@xxxxxxxxxxxxxxxx
> > www.krollontrack.com
> 
> --
> Roger
> 
> 
> 
> 
> _______________________________________________
> xfs mailing list
> xfs@xxxxxxxxxxx
> http://oss.sgi.com/mailman/listinfo/xfs

-- 
Carlos

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