A non-debugging log for bzr?

[Matthieu Moy]

John Arbash Meinel <john at arbash-meinel.com> writes:

> What granularity are you thinking Matthieu? Something *like*
> '~/.bzr.log' only just listing the specific commands? Any reason why
> ~/.bash_history doesn't work?

~/.bash_history is almost OK, but it doesn't work well if you had
several terminals, and it doesn't keep track of the status (whether
there have been an error or not), and of the working tree affected for
example.

Typical example being

me$ mail -s "please, merge from me and commit"

user$ bzr merge
user$ bzr commit
<User thinks: "What the hell is this Emacs window???">
<User closes the Emacs window. Hey, who's the master here?>
ERROR: Empty log message.

<User thinks: "OK, I commited as he asked">

user$ mail -s "done"


Later:

me$ mail -s "can you merge again?"

user$ bzr merge
ERROR: You have uncommited changes

<long discussion with the user arguing that he has just commited, and
me telling him that he did not>

(well, obviously, don't tailor a solution just for me, but that's just
an idea, I don't really _need_ it. If other users think it'd be
useful, it might be worth giving it a try)

-- 
Matthieu