From: "Mike Coleman" <tutufan@gmail.com>
To: "Nicolas Pitre" <nico@cam.org>
Cc: git@vger.kernel.org
Subject: Re: newbie questions about git design and features (some wrt hg)
Date: Wed, 31 Jan 2007 10:58:28 -0600 [thread overview]
Message-ID: <3c6c07c20701310858v488ebbd4k98cd14340661f086@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0701310959220.3021@xanadu.home>
On 1/31/07, Nicolas Pitre <nico@cam.org> wrote:
> Matt Mackall said himself that some core portion of hg have been
> rewritten in C in order to improve performances.
For what it's worth, sloccount reports the following:
git: 52K C, 17K Perl, 10K sh, 6K Tcl, 300 Python
hg: 14K Python, 700 C
Speculating wildly, I'd be surprised if the C part of git couldn't be
reduced below 5K, at a cost of an 8K increase in Perl (or Python), and
not more than a doubling of runtime. (This speculation is for
entertainment purposes only--I'm not suggesting a course of action.)
Mike
prev parent reply other threads:[~2007-01-31 16:58 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-30 16:20 newbie questions about git design and features (some wrt hg) Mike Coleman
2007-01-30 16:41 ` Johannes Schindelin
2007-01-30 16:55 ` Shawn O. Pearce
2007-01-31 1:55 ` Theodore Tso
2007-01-31 10:56 ` Jakub Narebski
2007-01-31 20:01 ` Junio C Hamano
2007-01-31 22:25 ` Matt Mackall
2007-01-31 23:58 ` Jakub Narebski
2007-02-01 0:34 ` Matt Mackall
2007-02-01 0:57 ` Jakub Narebski
2007-02-01 7:59 ` Simon 'corecode' Schubert
2007-02-01 10:09 ` Johannes Schindelin
2007-02-01 10:15 ` Simon 'corecode' Schubert
2007-02-01 10:49 ` Johannes Schindelin
2007-02-01 16:28 ` Linus Torvalds
2007-02-01 19:36 ` Eric Wong
2007-02-01 21:13 ` Linus Torvalds
2007-02-02 9:55 ` Jakub Narebski
2007-02-02 13:51 ` Simon 'corecode' Schubert
2007-02-02 14:23 ` Jakub Narebski
2007-02-02 15:02 ` Shawn O. Pearce
2007-02-02 15:38 ` Mark Wooding
2007-02-02 16:09 ` Jakub Narebski
2007-02-02 16:42 ` Linus Torvalds
2007-02-02 16:59 ` Jakub Narebski
2007-02-02 17:11 ` Linus Torvalds
2007-02-02 17:59 ` Brendan Cully
2007-02-02 18:19 ` Jakub Narebski
2007-02-02 19:28 ` Brendan Cully
2007-02-02 18:27 ` Giorgos Keramidas
2007-02-02 19:01 ` Linus Torvalds
2007-02-03 21:20 ` Giorgos Keramidas
2007-02-03 21:37 ` Matthias Kestenholz
2007-02-03 21:41 ` Linus Torvalds
2007-02-03 21:45 ` Jakub Narebski
2007-02-02 18:32 ` Linus Torvalds
2007-02-02 19:26 ` Brendan Cully
2007-02-02 19:42 ` Linus Torvalds
2007-02-02 19:55 ` Brendan Cully
2007-02-02 20:15 ` Jakub Narebski
2007-02-02 20:21 ` Linus Torvalds
2007-02-02 16:03 ` Matt Mackall
2007-02-02 17:18 ` Jakub Narebski
2007-02-02 17:37 ` Matt Mackall
2007-02-02 18:44 ` Jakub Narebski
2007-02-02 19:56 ` Jakub Narebski
2007-02-03 20:06 ` Brendan Cully
2007-02-03 20:55 ` Jakub Narebski
2007-02-03 21:00 ` Jakub Narebski
2007-01-30 17:44 ` Jakub Narebski
2007-01-30 18:06 ` Linus Torvalds
2007-01-30 19:37 ` Linus Torvalds
2007-01-30 18:11 ` Junio C Hamano
2007-01-31 3:38 ` Mike Coleman
2007-01-31 4:35 ` Linus Torvalds
2007-01-31 4:57 ` Junio C Hamano
2007-01-31 16:22 ` Linus Torvalds
2007-01-31 16:41 ` Johannes Schindelin
2007-01-31 7:11 ` Mike Coleman
2007-01-31 15:03 ` Nicolas Pitre
2007-01-31 16:58 ` Mike Coleman [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3c6c07c20701310858v488ebbd4k98cd14340661f086@mail.gmail.com \
--to=tutufan@gmail.com \
--cc=git@vger.kernel.org \
--cc=nico@cam.org \
/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.
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 NNTP newsgroup(s).