[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: git replace --edit for updating commit messages (was: Is it time to
From: |
Eli Zaretskii |
Subject: |
Re: git replace --edit for updating commit messages (was: Is it time to drop ChangeLogs?) |
Date: |
Thu, 28 Jul 2016 17:43:48 +0300 |
> From: Noam Postavsky <address@hidden>
> Date: Wed, 27 Jul 2016 21:35:34 -0400
> Cc: Robert Weiner <address@hidden>, Stefan Monnier <address@hidden>,
> emacs-devel <address@hidden>
>
> Doing git log became dramatically slower (packing the refs did not
> make much difference).
>
> Original repository:
>
> ~/src/emacs/emacs-master$ time git log --oneline | wc -l
> 126614
>
> real 0m5.435s
> user 0m3.157s
> sys 0m2.780s
>
> ~/src/emacs/emacs-master$ time git log --oneline | head >/dev/null
>
> real 0m0.009s
> user 0m0.003s
> sys 0m0.003s
>
>
> Repository with all commit messages replaced: (almost all, there were
> a few messages that lacked letters, so my upcasing script had no
> effect)
>
> ~/src/emacs/emacs-clone$ time git log --oneline | wc -l
> 126614
>
> real 0m49.337s
> user 0m8.270s
> sys 0m39.680s
>
> ~/src/emacs/emacs-clone$ time git log --oneline | head >/dev/null
>
> real 0m0.520s
> user 0m0.237s
> sys 0m0.250s
Thanks. But I think a more relevant timing would be one for something
like 1% to 10% of replaced messages, because we will never have all of
them replaced.