From: Eli Zaretskii <eliz@gnu.org>
To: "Andreas Röhler" <andreas.roehler@online.de>
Cc: justin@justinlilly.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: git source mirrors inactive
Date: Thu, 26 May 2011 06:16:33 -0400 [thread overview]
Message-ID: <E1QPXcH-0002W7-Ob@fencepost.gnu.org> (raw)
In-Reply-To: <4DDE0A0D.7080400@online.de> (message from Andreas Röhler on Thu, 26 May 2011 10:06:37 +0200)
> Date: Thu, 26 May 2011 10:06:37 +0200
> From: Andreas Röhler <andreas.roehler@online.de>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
> Emacs developers <emacs-devel@gnu.org>
>
> Thanks, below still an example pointing at the convenience of working
> from git:
>
> # time git log -n 2 python.el
> [...]
> real 0m0.122s
> user 0m0.020s
> sys 0m0.024s
>
> # time bzr log -l 2 python.el
> [...]
> real 0m29.459s
> user 0m24.554s
> sys 0m0.716s
It is meaningless to pick up a random command and compare based on
that command alone. Here's another meaningless comparison:
eliz@fencepost:~/bzr/emacs/trunk$ time bzr annotate src/xdisp.c > /dev/null
real 1m43.832s
user 1m25.740s
sys 0m3.110s
eliz@fencepost:~/git/emacs$ time git annotate src/xdisp.c > /dev/null
real 5m9.646s
user 4m18.400s
sys 0m3.580s
I don't know how frequently you need to know the last 2 changes of
python.el, but the number of times I needed to annotate xdisp.c during
the last 2 years is about twice a week. I will gladly trade a 29-sec
wait for 3.5 min wait. YMMV.
next prev parent reply other threads:[~2011-05-26 10:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 14:10 git source mirrors inactive Andreas Röhler
2011-05-25 14:52 ` Sven Joachim
2011-05-25 15:47 ` Andreas Röhler
2011-05-25 23:59 ` Stefan Monnier
2011-05-26 0:06 ` Justin Lilly
2011-05-26 5:49 ` Leo
2011-05-26 8:06 ` Andreas Röhler
2011-05-26 8:28 ` Werner LEMBERG
2011-05-26 10:16 ` Eli Zaretskii [this message]
2011-05-26 10:58 ` Andreas Röhler
2011-05-26 11:27 ` Eli Zaretskii
2011-05-27 15:01 ` Stefan Monnier
2011-05-27 15:11 ` Julien Danjou
2011-05-29 2:27 ` T.V. Raman
2011-05-26 6:04 ` Andreas Röhler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1QPXcH-0002W7-Ob@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=andreas.roehler@online.de \
--cc=emacs-devel@gnu.org \
--cc=justin@justinlilly.com \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).