Re: Question on how to submit changed code

Bill O'Donnell
2015-12-01T17:28:44Z

On Tue, Dec 01, 2015 at 05:33:35PM +0100, Carlos Maiolino wrote:
> I'm not an attorney, so take my suggestions with some caution.
>
> If you want to publish the code for be compliant with GPL, you might want to use
> some public repository like github, sourceforge, etc. but I think that even
> sending the patch to the list would be enough.
>
> Although, I think you only violate GPL if you're distributing the executables
> without the source code.

That's my understanding as well. I'd recommend submitting the patches to the list.
Even if they're NACKed, they're essentially "published". That said, if you have
other executables that are part of the offering, but are not public, you'd need
to make that source code public too.

>
> But, I'm not the best GPL geek, so I might be wrong
>
ditto. YMMV, so I'd consult a legal eagle. :P.

Bill
>
>
> On Tue, Dec 01, 2015 at 03:16:11PM +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?
> >
> >
> > Mike Epp, Senior Software Engineer
> >
> > Kroll Ontrack | 9023 Columbine Road, Eden Prairie, MN 55347
> > [1]mepp@krollontrack.com
> > [2]www.krollontrack.com
> >
> > This communication contains information that is confidential,
> > proprietary in nature, and may also be attorney-client privileged
> > and/or work product privileged. It is for the exclusive use of the
> > intended recipient(s). If you are not the intended recipient(s) or the
> > person responsible for delivering it to the intended recipient(s),
> > please note that any form of dissemination, distribution or copying of
> > this communication is strictly prohibited and may be unlawful. If you
> > have received this communication in error, please immediately notify
> > the sender and delete the original communication. Thank you for your
> > cooperation.
> >
> > Please be advised that neither Kroll, its affiliates, its employees or
> > agents accept liability for any errors, omissions or damages caused by
> > delays of receipt or by any virus infection in this message or its
> > attachments, or which may otherwise arise as a result of this e-mail
> > transmission.
> >
> > References
> >
> > 1. mailto:mepp@krollontrack.com
> > 2. http://www.krollontrack.com/ohttp:/www.krollontrack.com/
>
> > _______________________________________________
> > xfs mailing list
> > xfs@oss.sgi.com
> > http://oss.sgi.com/mailman/listinfo/xfs
>
>
> --
> Carlos
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs