From: "Nick Edelen" <sirnot@gmail.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Sam Vilain" <sam@vilain.net>,
"Shawn O. Pearce" <spearce@spearce.org>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Andreas Ericsson" <exon@op5.se>, "Jeff King" <peff@peff.net>
Subject: [RFC/PATCH INTRO] rev-cache
Date: Fri, 03 Jul 2009 16:13:25 +0100 [thread overview]
Message-ID: <op.uwhy8lhktdk399@sirnot> (raw)
Hi everyone,
I've been working on a revision caching system (with gsoc), and would be curious to get some feedback on it and it's (potential) installation into git. I believe the core mechanics of it are largely finished, but integration is still rather rough. I've tried to divide it into 4 self-contained patches -- each representing a working implemenation with incremental featuresets. The patchset is seperated as:
* basic - the simplest working revision cache implementation, with full docs and relavant tests
* objects - non-commit object caching + tests
* misc - extra (maintenance) features and refactor of object caching (requiring slight modification of some object structures)
* integration - (proof of concept) integration of rev-cache into rev-list, along with extensive tests
I'm afraid the first patch is rather big, as the topo-data encoding scheme is a smidgen complicated, but its effect on git's internals is very small -- it's less of a patch and more an addition of a few files. I know you guys prefer inline patches, but in view of the patchfile size I decided it'd be more prudent to include that seperately as an attachment. The only other caveat I can think of is that the tests currently require python, although that could change in future.
So yeah, I hope you find it interesting. Apologies if I'm breaking protocol...
- Nick
next reply other threads:[~2009-07-03 15:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-03 15:13 Nick Edelen [this message]
2009-07-20 23:48 ` [RFC/PATCH INTRO] rev-cache 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=op.uwhy8lhktdk399@sirnot \
--to=sirnot@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=exon@op5.se \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=sam@vilain.net \
--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).