From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] cvsimport: introduce -L<imit> option to workaround memory leaks
Date: Fri, 26 May 2006 07:29:49 +0200 [thread overview]
Message-ID: <e563o9$f6a$1@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.64.0605252204590.5623@g5.osdl.org
Linus Torvalds wrote:
> 200k commits at 6k commits per hour is about a day and a half (plus the
> occasional packing load). Taking that long to import a CVS archive is
> horrible. But I guess it _is_ several years of work, and I guess you
> really have to do it only once, but still.
And how parsecvs (which as far as I remember didn't have incremental mode)
compares wrt speed to git-cvsimport? It is supposed to be faster...
--
Jakub Narebski
Warsaw, Poland
next prev parent reply other threads:[~2006-05-26 5:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 11:38 [PATCH] cvsimport: introduce -L<imit> option to workaround memory leaks Martin Langhoff
2006-05-23 2:28 ` Linus Torvalds
2006-05-23 3:15 ` Martin Langhoff (CatalystIT)
2006-05-23 15:36 ` Theodore Tso
2006-05-23 16:05 ` Linus Torvalds
2006-05-23 16:25 ` Linus Torvalds
2006-05-26 0:42 ` Martin Langhoff
2006-05-26 5:20 ` Linus Torvalds
2006-05-26 5:29 ` Jakub Narebski [this message]
2006-05-26 6:02 ` Martin Langhoff
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='e563o9$f6a$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.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).