Re: bzr repository ready?

[Richard Stallman <rms@gnu.org>]

    BTW, one thing that the people who only have experience with CVS does
    not appreciate, is a changeset-oriented VCS, where the source base
    transforms on discrete and well defined steps. Among other things, this
    makes the Changelog unnecessary, as it turns to be the equivalent of
    `bzr log'.

They are not equivalent.  The ChangeLog files are included in the
checkout, so you can read them even when you are offline (which is
nearly all the time, for me).  `bzr log' requires contact with the
repository.

The obvious solution, running `bzr log' and saving output to a file
with every update, is not a full solution since it won't give the real
information about branches that were merged.

Is there a way to get all the information about what has been
merged into the current trunk?

Various directories have separate ChangeLog files.  Is that true also
for `bzr log', or is it one log for the whole package?

Another convenience with ChangeLog files is that we split them into
manageable-size parts.  It would be nice to have a script that would
do the same thing to the output of `bzr log', preferring to split
at the points where releases occurred.