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 0/6 (v2)] Suggested for PU: revision caching system to significantly speed up packing/walking
Date: Mon, 17 Aug 2009 11:19:46 +1200 [thread overview]
Message-ID: <4A889412.9090209@vilain.net> (raw)
In-Reply-To: <c77435a80908161547x4d2a9087qf439d1c30cc4fa99@mail.gmail.com>
Nick Edelen wrote:
> Well crap, in my infinite wisdom I replied with the final updated
> patchset to the wrong version :-/ I don't want to clog up the list
> with my stupid mistakes, but if you need me to I can resend them to
> v3.
>
Heh, that sure reads like a sentence written after midnight :-)
These all say v2, and the last lot was labeled as v3. And I see an
older submission labeled as v2 (8th August) and got duplicates of those
labeled as v3.
Are the ones attached to this the ones that are the best?
Sam
> But yeah, I've uploaded an updated version. This patchset:
> - fixes whitespace errors
> - adds _ondisk versions of structures to ensure portability
> - cleans up definitions/fix a typo
>
> Hope it works out for you all. Sorry about the mismatched reply.
>
> - Nick
>
next prev parent reply other threads:[~2009-08-16 23:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-08 7:31 [PATCH 0/6 (v2)] Suggested for PU: revision caching system to significantly speed up packing/walking Nick Edelen
2009-08-16 22:47 ` Nick Edelen
2009-08-16 23:19 ` Sam Vilain [this message]
2009-08-17 0:56 ` Nick Edelen
2009-08-17 8:16 ` Johannes Schindelin
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=4A889412.9090209@vilain.net \
--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 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.