Bug: log --forward prints merged comments first (was: log --forward printed wrongly in 0.8rc1 and doc request...)

[Jens Lund]

On Wednesday 26 April 2006 22:02, Jens Lund wrote:
> I have been playing a little around with 0.8rc1 and have only seen one
> issue:

The bug described below is still present in bzr.dev so I suppose it will be 
present in 0.8 as well if not fixed:

> When getting the log in forward order merged stuff is printed before the
> actual entry, it should be after. Example:
>
> bzr.dev$ bzr log -r-1.. --forward
>     ------------------------------------------------------------
>     merged: mbp at sourcefrog.net-20060426045253-0728376fb99879af
>     committer: Martin Pool <mbp at sourcefrog.net>
>     branch nick: bzr.mbp.40508
>     timestamp: Wed 2006-04-26 14:52:53 +1000
>     message:
>       Run ssh subprocess with SIGINT ignored, but in the same process
> group. (Malone #40508, #5987)
>     ------------------------------------------------------------
>     merged: mbp at sourcefrog.net-20060426063605-c66a7bf3f99f001c
>     committer: Martin Pool <mbp at sourcefrog.net>
>     branch nick: bzr.mbp.40508
>     timestamp: Wed 2006-04-26 16:36:05 +1000
>     message:
>       doc
> ------------------------------------------------------------
> revno: 1686
> committer: Canonical.com Patch Queue Manager<pqm at pqm.ubuntu.com>
> branch nick: +trunk
> timestamp: Wed 2006-04-26 07:45:44 +0100
> message:
>   (mbp) #40508 ignore interrupts in ssh child


> And then, please... It would be really great if the documentation
> (tutorial.txt in bzr.dev) was expanded to cover all the new functionality
> with repositories with several branches, checkouts, bound branches, in
> addition to describing possible ways to specify revisions, the default
> options/aliases in the config file, etc.

As a user I am very happy to see that work is now done on the documentation 
for the 0.8 release :-)