From: "Shawn O. Pearce" <spearce@spearce.org>
To: Nicolas Pitre <nico@cam.org>
Cc: Jeff King <peff@peff.net>,
Christian Couder <chriscool@tuxfamily.org>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Scott Chacon <schacon@gmail.com>,
Sam Vilain <sam.vilain@catalyst.net.nz>,
Petr Baudis <pasky@suse.cz>
Subject: Re: GitTogether topics status (4th of October)
Date: Tue, 7 Oct 2008 07:38:59 -0700 [thread overview]
Message-ID: <20081007143859.GJ8203@spearce.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0810062343000.3045@xanadu.home>
Nicolas Pitre <nico@cam.org> wrote:
> On Mon, 6 Oct 2008, Jeff King wrote:
>
> > 2. What needs refactoring?
> >
> > I occasionally run up against parts of the code that just make my
> > eyes bleed everytime I touch them. I think we've made significant
> > progress in maintanability and bug-avoidance with things like the
> > strbuf library, refactoring of remote and transport handling, etc.
> > What areas might still benefit from such refactoring?
>
> Tree object walking and commit object parsing. This is what's holding
> pack v4 performances back. But I think that Shawn will cover this
> already (I won't be there but I sent my thoughts about this to him).
Yup. A huge part of the pack v4 talk is going to be the parsing
code. Maybe 10 minutes of it will give the high level overview
of how pack v4 is organized, to explain why the parsing code is
a problem. :)
--
Shawn.
next prev parent reply other threads:[~2008-10-07 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-04 16:16 GitTogether topics status (4th of October) Christian Couder
2008-10-07 3:15 ` Jeff King
2008-10-07 3:46 ` Nicolas Pitre
2008-10-07 14:38 ` Shawn O. Pearce [this message]
2008-10-07 14:46 ` Shawn O. Pearce
2008-10-17 19:18 ` René Scharfe
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=20081007143859.GJ8203@spearce.org \
--to=spearce@spearce.org \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nico@cam.org \
--cc=pasky@suse.cz \
--cc=peff@peff.net \
--cc=sam.vilain@catalyst.net.nz \
--cc=schacon@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.