From: "Shawn O. Pearce" <spearce@spearce.org>
To: Nick Edelen <sirnot@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, Nicolas Pitre <nico@cam.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Sam Vilain <sam@vilain.net>,
Michael J Gruber <git@drmicha.warpmail.net>,
Jeff King <peff@peff.net>, Andreas Ericsson <exon@op5.se>,
Christian Couder <christian@couder.net>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH 7/6 (v4)] support for commit grafts, slight change to general mechanism
Date: Tue, 29 Sep 2009 09:34:14 -0700 [thread overview]
Message-ID: <20090929163414.GA25756@spearce.org> (raw)
In-Reply-To: <op.u0xtfzjrtdk399@sirnot.ed.ac.uk>
Nick Edelen <sirnot@gmail.com> wrote:
> Adds support for graft commits in rev-cache (w/ test), and slightly alters
> graft mechanism. Before, parse_commit() checked the graft list on every
> commit. Now register_commit_graft() preemptively loads graft commits into
> memory, and sets a new 'graft' flag in the object. This allows awareness of
> the commits' medical history without searching a (normally private) array upon
> each commit.
...
> diff --git a/builtin-rev-cache.c b/builtin-rev-cache.c
> index 4c1766d..b36bc39 100644
This doesn't apply against ne/rev-cache^, and I don't have the
blobs in my repostiory. So I'm dropping this patch and will wait
for a resend of the series or something...
--
Shawn.
next prev parent reply other threads:[~2009-09-29 16:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-07 14:11 [PATCH 7/6 (v4)] support for commit grafts, slight change to general mechanism Nick Edelen
2009-09-27 22:44 ` Nick Edelen
2009-09-29 16:34 ` Shawn O. Pearce [this message]
2009-09-30 8:00 ` Chris Johnsen
2009-10-19 20:31 ` Nick Edelen
2009-10-21 9:15 ` Thomas Rast
2009-10-21 13:44 ` Thomas Rast
2009-10-27 21:11 ` Nick Edelen
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=20090929163414.GA25756@spearce.org \
--to=spearce@spearce.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=christian@couder.net \
--cc=exon@op5.se \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nico@cam.org \
--cc=peff@peff.net \
--cc=sam@vilain.net \
--cc=sirnot@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.