git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Michael Haggerty" <mhagger@alum.mit.edu>,
	git@vger.kernel.org, "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>,
	"Thomas Rast" <tr@thomasrast.ch>
Subject: Re: [PATCH 2/2] log: do not shorten decoration names too early
Date: Fri, 22 May 2015 17:38:53 -0400	[thread overview]
Message-ID: <20150522213853.GA29804@peff.net> (raw)
In-Reply-To: <xmqqmw0we2b7.fsf@gitster.dls.corp.google.com>

On Fri, May 22, 2015 at 02:21:16PM -0700, Junio C Hamano wrote:

> I ended up doing it as a variant of the latter, "free unless we have
> v->buffer pointing at it".

Thanks, this version looks good to me minus one micro-nit below.

> Sorry for a long delay.

No problem. I'm sometimes amazed you find time to write any patches at
all. :)

> -- >8 --
> Subject: [PATCH] commit-slab: introduce slabname##_peek() function
> 
> There is no API to ask "Does this commit have associated data in
> slab?".  If an application wants to (1) parse just a few commits at
> the beginning of a process, (2) store data for only these commits,
> and then (3) start processing many commits, taking into account the
> data stored (for a few of them) in the slab, the application would
> use slabname##_at() to allocate a space to store data in (2), but
> there is no API other than slabname##_at() to use in step (3).  This
> allocates and wasts new space for these commits the caller is only
> interested in checking if they have data stored in step (2).

s/wasts/wastes/

-Peff

      reply	other threads:[~2015-05-22 21:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-13 13:11 "HEAD -> branch" decoration doesn't work with "--decorate=full" Michael Haggerty
2015-05-13 14:51 ` Junio C Hamano
2015-05-13 15:26   ` Michael J Gruber
2015-05-13 17:11 ` Junio C Hamano
2015-05-13 17:13   ` Junio C Hamano
2015-05-13 19:40     ` [PATCH 2/2] log: do not shorten decoration names too early Junio C Hamano
2015-05-14  6:33       ` Jeff King
2015-05-14 17:37         ` Junio C Hamano
2015-05-14 17:49           ` Jeff King
2015-05-14 18:01             ` Junio C Hamano
2015-05-14 18:10               ` Jeff King
2015-05-14 21:49           ` Junio C Hamano
2015-05-14 21:54             ` Jeff King
2015-05-14 22:25               ` Junio C Hamano
2015-05-14 22:33                 ` Jeff King
2015-05-22 21:21                   ` Junio C Hamano
2015-05-22 21:38                     ` Jeff King [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=20150522213853.GA29804@peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mhagger@alum.mit.edu \
    --cc=pclouds@gmail.com \
    --cc=tr@thomasrast.ch \
    /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).