From: Sam Vilain <sam@vilain.net>
To: Nick Edelen <sirnot@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, Nicolas Pitre <nico@cam.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Michael J Gruber <git@drmicha.warpmail.net>,
Jeff King <peff@peff.net>,
"Shawn O. Pearce" <spearce@spearce.org>,
Andreas Ericsson <exon@op5.se>,
Christian Couder <christian@couder.net>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH 5/6 (v4)] full integration of rev-cache into git, completed test suite
Date: Tue, 08 Sep 2009 09:06:04 +1200 [thread overview]
Message-ID: <1252357564.5969.4.camel@maia.lan> (raw)
In-Reply-To: <op.uzv4covmtdk399@sirnot.private>
On Mon, 2009-09-07 at 16:11 +0200, Nick Edelen wrote:
> This last patch
^^ You don't need to write comments like "This patch"; in the history
such words are meaningless.
> provides a working integration of rev-cache into the revision
> walker, along with some touch-ups:
> - integration into revision walker and list-objects
> - tweak of object generation
"tweak" ?
> - more fluid handling of damaged cache slices
What does this mean?
> - numerous tests for both features from the previous patch, and the
> integration's integrity
> 'Integration' is rather broad -- a more detailed description follows for each
> aspect:
> - rev-cache
> the traversal mechanism is updated to handle many of the non-prune options
> rev-list does (date limiting, slop-handling, etc.), and is adjusted to allow
> for non-fatal cache-traversal failures.
>
> - revision walker
> both limited and unlimited traversal attempt to use the cache when possible,
> smoothly falling back if it's not.
>
> - list-objects
> object listing does not recurse into cached trees, and has been adjusted to
> guarantee commit-tag-tree-blob ordering.
This is quite a long commit message. Is the above detail all useful?
Can it be split into one patch for each of the above integrations?
> Signed-off-by: Nick Edelen <sirnot@gmail.com>
Sam
next prev parent reply other threads:[~2009-09-07 21:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 12:31 [PATCH 5/6 (v4)] full integration of rev-cache into git, completed test suite Nick Edelen
2009-08-18 11:51 ` Nick Edelen
2009-08-21 4:48 ` Nick Edelen
2009-09-07 14:11 ` Nick Edelen
2009-09-07 21:06 ` Sam Vilain [this message]
2009-09-08 22:24 ` Nick Edelen
2009-09-30 7:53 ` Chris Johnsen
2009-09-30 8:09 ` Johannes Sixt
2009-10-02 22:12 ` Nick Edelen
2009-10-19 20:30 ` 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=1252357564.5969.4.camel@maia.lan \
--to=sam@vilain.net \
--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=sirnot@gmail.com \
--cc=spearce@spearce.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).