[impdev] GPL requirements and the ChangeLog

Jacek Antonelli jacek.antonelli at gmail.com
Thu Sep 3 13:37:14 PDT 2009


On Thu, Sep 3, 2009 at 11:11 AM, Adric R<hakushakukun at gmail.com> wrote:
> Is there any set format we need to follow when displaying the notice, i.e.
> do we need to comment the specific sections, or just add "modifed by
> so-and-so on such-and-such date" to the header?

The GPL doesn't seem to require a specific format, just as long as it
says that we modified it, and the date we did. So a script that adds a
little notice to the header should be fine. Something like this:

* [...]
* ALL LINDEN LAB SOURCE CODE IS PROVIDED "AS IS." LINDEN LAB MAKES NO
* WARRANTIES, EXPRESS, IMPLIED OR OTHERWISE, REGARDING ITS ACCURACY,
* COMPLETENESS OR PERFORMANCE.
* $/LicenseInfo$
*
* History of changes:
*   * McCabe Maxsted, 2009-09-03. Replaced code that was eaten by the
*     rabid weasle.
*   * Jacek Antonelli, 2009-09-01. Imported experimental rabid weasle
*     patch from Meerkat.
*/

The description of what changed might not be strictly necessary, but
we might as well include it, especially if a script is doing the work.

> I support the lazy option, for the record :) (although the idea of having
> commits just for adding this info sounds kinda awkward, if I read your
> workflow right. Is it possible to script a custom git command instead?)

Sorry, I should have explained better. The Git hook would modify the
ChangeLog and other files after you've entered the log message, but
before any commit is stored. So, there wouldn't be an extra commit,
just some extra changes magically added in the original commit.

-Jacek

P.S. Let's use bottom-posting or inline replying for the mailing list, please.



More information about the ImpDev mailing list