On May 16, 2:30 am, simon.k...@uni-jena.de wrote:
> Hi Michael,
>
> On 15 Mai, 09:52, mabshoff <mabsh...@googlemail.com> wrote:
>
> > I am not sure I understand the question, but there is no need to
> > provide a diff or anything like that. It is sufficient just to put the
> > modified files into the spkg.
>
> Now I am puzzled.
>
> The MeatAxe sources have a COPYING file that states:
> ----------------------
> GNU GENERAL PUBLIC LICENSE
> TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
> ...
> 2. You may modify your copy or copies of the Program or any portion
> of it, thus forming a work based on the Program, and copy and
> distribute such modifications or work under the terms of Section 1
> above, provided that you also meet all of these conditions:
>
> a) You must cause the modified files to carry prominent notices
> stating that you changed the files and the date of any change.
> ...
> -----------------------
>
> So, according to 2.a), I *must* have a diff file or something like
> that. Or not?
No. When you change foo.c you
(a) should add your name to the list of copyright holders for non-
trivial changes
(b) add a comment on what you changed, i.e. "changed bar to baz to
deal with frobnor"
Most people don't even do that, but use version control for changes.
Otherwise pretty much any file would become littered with changelogs,
etc. It is also quite common to have a global changelog where each
commit produces and entry listing files touched and changes made.
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
