Re: ChangeLogs in the elpa branch

[Eli Zaretskii <eliz@gnu.org>]

> From: Andreas Schwab <schwab@linux-m68k.org>
> Date: Tue, 27 Sep 2011 10:57:22 +0200
> Cc: Michael Albinus <michael.albinus@gmx.de>,
> 	Stefan Monnier <monnier@IRO.UMontreal.CA>, emacs-devel@gnu.org
> 
> > But editing the commit logs beyond that goes against a principle that
> > is somewhat carved in stone: "Don't modify the commit logs history."
> 
> The principle is actually: "Don't modify published history."  It is
> perfectly ok to edit commits locally until you are happy with them
> before publishing them.

If your bzr branch is not bound, then your log messages will be
invisible anyway after merging to mainline (unless people actually
_want_ to see logs from non-mainline history); what matters is the log
you write when you merge.  If your branch _is_ bound, then there are
no local commits.  (If you are thinking about "bzr ci --local", then
these again look after pushing as non-mainline commits, so this option
doesn't change the basic facts.)

I suspect that people who care about lack of the ability to edit log
messages are talking about the latter situation.  So the "you can edit
non-published history" stance does not help them.