git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Edelen <sirnot@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2009, #04; Wed, 16)
Date: Thu, 17 Sep 2009 18:03:28 +0100	[thread overview]
Message-ID: <c77435a80909171003g3e2fe9f6sa2e528459fa790f0@mail.gmail.com> (raw)
In-Reply-To: <7v1vm6kskd.fsf@alter.siamese.dyndns.org>

> * ne/rev-cache (2009-09-07) 7 commits
>  . support for commit grafts, slight change to general mechanism
>  . support for path name caching in rev-cache
>  . full integration of rev-cache into git, completed test suite
>  . administrative functions for rev-cache, start of integration into git
>  . support for non-commit object caching in rev-cache
>  . basic revision cache system, no integration or features
>  . man page and technical discussion for rev-cache
>
> Replaced but I do not think this is ready for 'pu' yet.

Er, what direction would you suggest taking to bring this patchset up
to scratch?  I've run several tests locally, and it seems to work as
intended, but I wouldn't assert that I've taken every possibility into
account.  Should I submit some tests/benchmarks in more real-world
environments?  I'm afraid that I'm not personally among the intended
audience for this, so I don't have a really solid idea of how this
might perform in the wild.

 - Nick

      parent reply	other threads:[~2009-09-17 17:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17  6:12 What's cooking in git.git (Sep 2009, #04; Wed, 16) Junio C Hamano
2009-09-17  9:26 ` Sverre Rabbelier
2009-09-17 17:03 ` Nick Edelen [this message]

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=c77435a80909171003g3e2fe9f6sa2e528459fa790f0@mail.gmail.com \
    --to=sirnot@gmail.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).