History editing (Was: Will re-basing support be added into Bazaar core?)

[David Timothy Strauss]

----- "Andrew Cowie" <andrew at operationaldynamics.com> wrote:

> While the end result *diff* is what we [ie any arbitrary upstream
> maintainer] review when considering a contributor, once accepted the
> individual revisions retain their identity *and their revision
> message*.
> 
> 
> Which means (taking Paul's example above) that if the 3rd revision
> contains a huge amount of acceptable work, then future runs of:
> 
> $ bzr gannotate
> 
> are, for a *long* time to come, going to have
> 
> "No more time today, committing so I can pick it up tomorrow"
> 
> as the revision message associated with that piece of code.
> 
> Not very useful.

I think the obvious solution is to have gannotate walk up the tree and show commit messages from parent revisions, too.