From: Nicolas Pitre <nico@cam.org>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Keith Packard <keithp@keithp.com>,
Linus Torvalds <torvalds@osdl.org>, git <git@vger.kernel.org>
Subject: Re: Why so much time in the kernel?
Date: Fri, 16 Jun 2006 14:07:08 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0606161406260.16002@localhost.localdomain> (raw)
In-Reply-To: <9e4733910606161044h736c9675kc91ff77904c5a1d0@mail.gmail.com>
On Fri, 16 Jun 2006, Jon Smirl wrote:
> On 6/16/06, Keith Packard <keithp@keithp.com> wrote:
> > On Fri, 2006-06-16 at 13:00 -0400, Jon Smirl wrote:
> > > Is it a crazy idea to read the cvs files, compute an sha1 on each
> > > expanded delta and then write the delta straight into a pack file? Are
> > > the cvs and git delta formats the same? What about CVS's forward and
> > > reverse delta use?
> >
> > At this point, merging blobs into packs isn't a significant part of the
> > computational cost. parsecvs is spending all of its time in the
> > quadratic traversal of the diff chains; fixing that to emit all of the
> > versions in a single pass should speed up that part of the conversion
> > process dramatically.
>
> That's not true for the state I am in. cvsps can compute the changeset
> tree in 15 minutes, cvs2svn can compute their version in a couple of
> hours. cvs2svn builds a much better tree.
Did you try parsecvs recently?
Nicolas
next prev parent reply other threads:[~2006-06-16 18:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-16 14:49 Why so much time in the kernel? Jon Smirl
2006-06-16 15:06 ` Linus Torvalds
2006-06-16 15:25 ` Jon Smirl
2006-06-16 16:09 ` Linus Torvalds
2006-06-16 17:00 ` Jon Smirl
2006-06-16 17:09 ` Jakub Narebski
2006-06-16 17:29 ` Keith Packard
2006-06-16 17:44 ` Jon Smirl
2006-06-16 18:02 ` Keith Packard
2006-06-16 18:07 ` Nicolas Pitre [this message]
2006-06-16 18:32 ` Linus Torvalds
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=Pine.LNX.4.64.0606161406260.16002@localhost.localdomain \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=jonsmirl@gmail.com \
--cc=keithp@keithp.com \
--cc=torvalds@osdl.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).