From: Carlos Maiolino <cmaiolino@redhat.com>
To: Roger Willcocks <roger@filmlight.ltd.uk>
Cc: "Epp, Mike" <MEpp@KrollOntrack.com>, "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: Question on how to submit changed code
Date: Tue, 1 Dec 2015 18:44:37 +0100 [thread overview]
Message-ID: <20151201174437.GA4037@redhat.com> (raw)
In-Reply-To: <1448991660.16687.159.camel@montana.filmlight.ltd.uk>
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@krollontrack.com
> > www.krollontrack.com
>
> --
> Roger
>
>
>
>
> _______________________________________________
> 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
next prev parent reply other threads:[~2015-12-01 17:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 15:16 Question on how to submit changed code Epp, Mike
2015-12-01 16:33 ` Carlos Maiolino
2015-12-01 17:28 ` Bill O'Donnell
2015-12-01 17:41 ` Roger Willcocks
2015-12-01 17:44 ` Carlos Maiolino [this message]
2015-12-01 17:47 ` Carlos Maiolino
2015-12-01 18:03 ` Roger Willcocks
2015-12-01 18:10 ` Epp, Mike
2015-12-01 22:27 ` Dave Chinner
2015-12-01 17:53 ` Bill O'Donnell
2015-12-01 22:39 ` Dave Chinner
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=20151201174437.GA4037@redhat.com \
--to=cmaiolino@redhat.com \
--cc=MEpp@KrollOntrack.com \
--cc=roger@filmlight.ltd.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.