On Wed, Jun 01, 2011 at 04:15:31PM +0100, Markos Chandras wrote: > On 01/06/2011 04:08 ????, Peter Volkov wrote: > > ?? ??????, 30/05/2011 ?? 14:55 -0700, Brian Harring ??????????: > >> The problem is, that's a *fuzzy* definition. > > > > Ok, let's start with something and then we'll add more items if > > required. Currently I'd like to propose following text: > > > > The ChangeLog must be updated with each commit. The only possible > > relaxations for this rule are: > > > > 1. Nonfunctional whitespace changes > > 2. Changes in comments (lines starting with # in ebuild, or leading text > > in patches) > > 3. Manifest updates > > 4. Changes in ChageLog itself ;) > > > > Something unclear? Anything else?
I think these are reasonable.
> > --
> > Peter.
> Maybe typos in e{log,warn,info} messages and/or typos in general (
> variables, functions etc )
But typos in variables and functions (which in most cases _imply_
functional changes) are generally bugs which should be mentioned in
the ChangeLog. Typos in informational messages (e{log,warn,info})
might also affect the user and thus be `functional' indirectly. I
think that the 4-item list is complete enough ;-).
--
binki
Look out for missing or extraneous apostrophes!
pgpFCdFauEa5F.pgp
Description: PGP signature
