From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Linus Torvalds" <torvalds@osdl.org>
Cc: git <git@vger.kernel.org>
Subject: Re: Why so much time in the kernel?
Date: Fri, 16 Jun 2006 13:00:05 -0400 [thread overview]
Message-ID: <9e4733910606161000t53328571u10a350eca894ccdc@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0606160906250.5498@g5.osdl.org>
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? While this is going on, track the
branches/changsets in memory and then finish up by writing these trees
into the pack file too. This should take no more ram than cvsps needs
currently.
This leaves the packfile is a non-optimal format but a repack should
fix that, right?
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2006-06-16 17:00 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 [this message]
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
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=9e4733910606161000t53328571u10a350eca894ccdc@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=git@vger.kernel.org \
--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).