From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, git-dev@github.com
Subject: Re: [PATCH] parse_object: try internal cache before reading object db
Date: Fri, 6 Jan 2012 17:46:19 -0500 [thread overview]
Message-ID: <20120106224619.GA13654@sigill.intra.peff.net> (raw)
In-Reply-To: <7vmxa0ih6s.fsf@alter.siamese.dyndns.org>
On Fri, Jan 06, 2012 at 02:45:15PM -0800, Junio C Hamano wrote:
> > Did you want to leave the parse_object optimization until next cycle,
> > too? It's not loosening checks, but it's such a core piece of code that
> > it makes me nervous somebody somewhere is abusing "struct object" in a
> > way that will break it.
>
> I was just updating the "What's cooking" report and my current thinking is
> that we should keep all three in "next" to give it a bit of exposure for
> now, and merge them to "master" early in the 1.7.10 cycle.
That sounds perfect. Thanks.
-Peff
next prev parent reply other threads:[~2012-01-06 22:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 21:00 [PATCH] parse_object: try internal cache before reading object db Jeff King
2012-01-05 21:35 ` Junio C Hamano
2012-01-05 21:49 ` Jeff King
2012-01-05 21:55 ` Junio C Hamano
2012-01-05 22:18 ` Jeff King
2012-01-06 19:16 ` Jeff King
2012-01-06 21:27 ` Junio C Hamano
2012-01-06 22:33 ` Jeff King
2012-01-06 22:45 ` Junio C Hamano
2012-01-06 22:46 ` Jeff King [this message]
2012-01-06 19:17 ` [PATCH 1/2] upload-pack: avoid parsing objects during ref advertisement Jeff King
2013-01-18 23:12 ` Junio C Hamano
2013-01-24 7:50 ` Jeff King
2013-01-24 17:25 ` Junio C Hamano
2013-01-29 8:10 ` Shawn Pearce
2013-01-29 8:14 ` Jeff King
2012-01-06 19:18 ` [PATCH 2/2] upload-pack: avoid parsing tag destinations Jeff King
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=20120106224619.GA13654@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git-dev@github.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).