Re: GPL development etiquette

Bob Tennent writes:
The maintainer should be doing that. The Changelog isn't yours to change.

If you are creating a fork (which should be avoided if possible) you should
document your changes in the changelog. You will be supporting the fork
from now on: it's your changelog now. If you are submitting a patch let
the maintainer deal with the changelog.
--
John Hasler
john@xxxxxxxxxx
Dancing Horse Hill
Elmwood, WI USA
.

Relevant Pages

  • Re: [PATCH 2.6.11-rc4-mm1] connector: Add a fork connector
    ... On Thu, 2005-02-24 at 11:24 +0100, Guillaume Thouvenin wrote: ... It allows to several user space ... > applications to be informed when a fork occurs in the kernel. ... ChangeLog before you will push it upstream. ...
    (Linux-Kernel)
  • Re: NitroHack 4.0.0 release
    ... Just going from the changelog, it looks to be exactly what the nethack ... community needs and has been lacking: a fork that's conservative ... You make it sound like it's bad to be a variant. ... architecture base (as a prerequisite for a source code base for a ...
    (rec.games.roguelike.nethack)
  • PySimpleSOAP 1.05a released
    ... interfaces, aimed to be as small and easy as possible, supporting most ... common functionality. ... Version 1.05a changelog: ...
    (comp.lang.python.announce)