A non-debugging log for bzr?

[John Arbash Meinel]

Matthieu Moy wrote:
> Hi,
> 
> Is there any way to have bzr make a non-debugging, non-verbose log.
> 
> Just something recording which action have been made with bzr, at what
> time, and in which directory (and whether it failed or not).
> 
> Indeed, I'm facing the old well-known problems of beginners swearing
> that they did/did not run such or such command, and then trying to
> understand how they mixed up their archive ;-).
> 
> But this could also be useful in the case of non-beginners, to keep
> track of what commands have been ran (well, the branch history is here
> for that, but it records only merges and commits).
> 
> Thanks,
> 

Touching on what Andrew King went through. What about having a simple
log of all basic actions that are applied to a repository. This is meant
as sort of a append-only line-wise actions taken. Possibly as
large-grained as 'adding revisions X,Y,Z...'
I don't think we want a complete write-ahead log, as I would like this
to not become a bottleneck. Extra points if we find a way to write stuff
to it asynchronously.

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

There is something that could be worthwhile here, and depending on what
you want it could be done as a simple plugin (hijack
bzrlib.commands.main, and just log whatever commands go through there).

John
=:->

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 254 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060922/3f828421/attachment.pgp