Re: Abolishing ChangeLog files

[Eli Zaretskii]

> Date: Fri, 29 Mar 2013 19:07:50 +0400
> From: Dmitry Gutov <address@hidden>
> CC: address@hidden, Stefan Monnier <address@hidden>
> 
> On 29.03.2013 10:10, Eli Zaretskii wrote:
> >> Date: Fri, 29 Mar 2013 08:45:44 +0300
> >> From: Eli Zaretskii <address@hidden>
> >> Cc: address@hidden, address@hidden
> > 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.)
> >
> 
> If you mean that it writes to ~/bazaar/.bzr.log, then it doesn't, here. 
> The file exists, but all the entries there are from September 1st last 
> year. Not important, just an aside.

It's ~/.bzr.log, not ~/bazaar/.bzr.log.

> Thank you. It inspired me to run the same non-interactive tests you did, 
> and indeed the full 'git log lisp\progmodes\ruby-mode.el > NUL' 
> invocation is non-instantaneous every time, and it's on the same order 
> of magnitude as 'bzr log', although the latter takes twice as long:
> 
> emacs-git-savannah>timep git log lisp\progmodes\ruby-mode.el > NUL
> 
> real    00h00m04.652s
> user    00h00m00.000s
> sys     00h00m00.015s
> 
> emacs-bzr\trunk>timep bzr log lisp\progmodes\ruby-mode.el > NUL
> 
> real    00h00m08.269s
> user    00h00m07.878s
> sys     00h00m00.280s
> 
> But! Git starts streaming output just as soon as it can, hence my 
> earlier impression that the command is instantaneous.

That only matters if you want the first few revisions.  What if you
want the last?

>  > I did, just now: (...)
> 
> I tried it, too, and here Git wins hands-down.
> 
> Here's how long it takes to update both when they are already up-to-date 
> (staging a situation when they're the same number of revisions 
> out-of-date is harder):
> 
> emacs-git-savannah>timep git pull
> Already up-to-date.
> 
> real    00h00m02.139s
> user    00h00m00.000s
> sys     00h00m00.031s
> 
> emacs-bzr\trunk>timep bzr update
> Дерево в актуальной ревизии 112180 ветви 
> bzr+ssh://address@hidden/emacs/trunk
> 
> 
> real    00h00m09.963s
> user    00h00m00.343s
> sys     00h00m00.202s

So you wasted the whole of 7 sec to know that your tree is up to
date.  Big deal!

> Before that, I updated this Bazaar clone from a several-days-old 
> revision, and it took 4 minutes.

Your network needs an urgent upgrade.

> I don't have a similar result for Git 
> to compare, but considering it cloned the whole history in 30 minutes 
> (same as on your machine)

You are mistaken, a full clone took me 3 hours, not 30 min.