git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Nicolas Pitre" <nico@cam.org>
Cc: "Jon Smirl" <jonsmirl@gmail.com>, git <git@vger.kernel.org>
Subject: Re: packs and trees
Date: Wed, 21 Jun 2006 07:41:57 +1200	[thread overview]
Message-ID: <46a038f90606201241x3dec242dicde245a24c3ab9ab@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0606201102410.3377@localhost.localdomain>

On 6/21/06, Nicolas Pitre <nico@cam.org> wrote:
> 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?

I was thinking of the "repacking disconnected objects" thread, but now
I see it did have a solution in listing all the objects and paths. I
take that back.

If you are asking about the ext3 performance problems, I think Linus
discussed that a while ago, why unpacked repos are slow (in addition
to huge), and there were some suggestions of using hashed directory
indexes.

cheers,


martin

  reply	other threads:[~2006-06-20 19:42 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
2006-06-20 19:41     ` Martin Langhoff [this message]
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=46a038f90606201241x3dec242dicde245a24c3ab9ab@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jonsmirl@gmail.com \
    --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).