From: Nicolas Pitre <nico@cam.org>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Jon Smirl <jonsmirl@gmail.com>, git <git@vger.kernel.org>
Subject: Re: packs and trees
Date: Tue, 20 Jun 2006 11:03:24 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0606201102410.3377@localhost.localdomain> (raw)
In-Reply-To: <46a038f90606192313l16b16132r1523f5e05ae1566a@mail.gmail.com>
On Tue, 20 Jun 2006, Martin Langhoff wrote:
> On 6/20/06, Jon Smirl <jonsmirl@gmail.com> wrote:
> > The plan is to modify rcs2git from parsecvs to create all of the git
> > objects for the tree.
>
> Sounds like a good plan. Have you seen recent discussions about it
> being impossible to repack usefully when you don't have trees (and
> resulting performance problems on ext3).
What do you mean?
Nicolas
next prev parent reply other threads:[~2006-06-20 15:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 5:57 packs and trees Jon Smirl
2006-06-20 6:13 ` Martin Langhoff
2006-06-20 14:35 ` Jon Smirl
2006-06-20 15:18 ` Keith Packard
2006-06-20 16:33 ` Jon Smirl
2006-06-20 15:03 ` Nicolas Pitre [this message]
2006-06-20 19:41 ` Martin Langhoff
2006-06-20 20:51 ` Nicolas Pitre
2006-06-21 3:54 ` Linus Torvalds
2006-06-21 15:32 ` David Lang
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.0606201102410.3377@localhost.localdomain \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=jonsmirl@gmail.com \
--cc=martin.langhoff@gmail.com \
/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).