Re: Abolishing ChangeLog files

[Thierry Volpiatto]

Eli Zaretskii <address@hidden> writes:

>> Date: Fri, 29 Mar 2013 08:45:44 +0300
>> From: Eli Zaretskii <address@hidden>
>> Cc: address@hidden, address@hidden
>> 
>> > Date: Fri, 29 Mar 2013 02:42:51 +0400
>> > From: Dmitry Gutov <address@hidden>
>> > CC: address@hidden, address@hidden
>> > 
>> > > I wrote that program myself.  Unix 'time' cannot be ported, because it
>> > > uses too many Posix APIs.
>> > 
>> > Since you don't seem inclined to distribute it, you won't get exact 
>> > numbers from me.
>> 
>> You never asked.  I can send the source to you privately, if you
>> want.
>
> Btw: bzr logs all of its times in .bzr.log, so you don't need any
> additional programs to time it.  (I wish git had such a comprehensive
> logging facility, it proved invaluable for me quite a few times in the
> past.)

>From the bzr documentation:
http://doc.bazaar.canonical.com/beta/en/user-reference/log-help.html

,----
| bzr log -v on a branch with lots of history is currently very slow. A
| fix for this issue is currently under development. With or without that
| fix, it is recommended that a revision range be given when using the -v
| option.
`----

Each time I tried bzr log (when I had bzr) it ends up With C-c because
it was too long (against the emacs trunk), so I always had a copy of
emacs converted to hg or git to be able to see the full logs.
So no need to use time to measure the slowness (at least for me).

-- 
Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997