Git development
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Anders Kaseorg <andersk@ksplice.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
	git@vger.kernel.org, "SZEDER Gábor" <szeder@ira.uka.de>,
	"Kirill Smelkov" <kirr@mns.spb.ru>,
	"Thomas Rast" <trast@student.ethz.ch>
Subject: Re: [PATCH] describe: Don’t look up commits with --exact-match
Date: Mon, 6 Dec 2010 11:47:23 -0600	[thread overview]
Message-ID: <20101206174723.GB6272@burratino> (raw)
In-Reply-To: <alpine.DEB.2.02.1012061159500.23348@dr-wily.mit.edu>

Anders Kaseorg wrote:

> Yeah.  Okay, I see that “lookup” implies unpacking, as opposed to “find”, 
> which doesn’t.  The important part is to avoid the find, of course, 
> because the I/O is expensive.
>
> Anyway, here’s a series with that change split out.

Thanks.

In theory finding an object would only require looking at the pack
index (and directory listings), but find_pack_entry does

		/*
		 * We are about to tell the caller where they can
		 * locate the requested object.  We better make
		 * sure the packfile is still here and can be
		 * accessed before supplying that answer, as
		 * it may have been deleted since the index
		 * was loaded!
		 */

which spoils that plan.

Your original use of the word "lookup" seemed sane, too; I was just
fishing for a more detailed explanation.

Reviewed-by: Jonathan Nieder <jrnieder@gmail.com>

> -- 8< --
> From 2ad1e58b8f6e9c117c77748b6e8b85227d9d5412 Mon Sep 17 00:00:00 2001
[...]

For the future: this does not follow the preferred patch format (one
patch per message, each of the form "description/---/diff").  In this
case I am guessing it won't be much trouble to massage on the
receiving end, so no terrible loss.

  reply	other threads:[~2010-12-06 17:47 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17 23:33 [PATCH] describe: Don’t look up commits with --exact-match Anders Kaseorg
2010-12-03  8:43 ` Jonathan Nieder
2010-12-06  7:19   ` Anders Kaseorg
2010-12-06  7:22     ` Anders Kaseorg
2010-12-06  7:32     ` Jonathan Nieder
2010-12-06 10:53       ` Thomas Rast
2010-12-06 17:28       ` Anders Kaseorg
2010-12-06 17:47         ` Jonathan Nieder [this message]
2010-12-07  9:58         ` SZEDER Gábor
2010-12-07 18:22           ` [PATCH 1/2] describe: Use for_each_rawref Anders Kaseorg
2010-12-07 18:22             ` [PATCH 2/2] describe: Don’t look up commits with --exact-match Anders Kaseorg
2010-12-07 18:26             ` [PATCH 1/2] describe: Use for_each_rawref Anders Kaseorg
2010-12-07 19:49               ` Junio C Hamano
2010-12-07 21:59                 ` Junio C Hamano
2010-12-07 18:39         ` [PATCH] describe: Don’t look up commits with --exact-match Junio C Hamano
2010-12-08  4:41           ` Anders Kaseorg
2010-12-08  4:42             ` [PATCH v2 1/4] describe: Use for_each_rawref Anders Kaseorg
2010-12-08  4:43               ` [PATCH v2 2/4] describe: Don’t use a flex array in struct commit_name Anders Kaseorg
2010-12-08  4:43               ` [PATCH v2 3/4] describe: Store commit_names in a hash table by commit SHA1 Anders Kaseorg
2010-12-08 18:23                 ` [PATCH v2.1 " Anders Kaseorg
2010-12-08 22:50                   ` Junio C Hamano
2010-12-08  4:46               ` [PATCH v2 4/4] describe: Delay looking up commits until searching for an inexact match Anders Kaseorg
2010-12-08 22:50                 ` Junio C Hamano
2010-12-08 23:47                   ` Anders Kaseorg
2010-12-09  6:42                     ` [PATCH v3 1/4] describe: Use for_each_rawref Anders Kaseorg
2010-12-09  6:43                       ` [PATCH v3 2/4] describe: Don’t use a flex array in struct commit_name Anders Kaseorg
2010-12-09  6:46                       ` [PATCH v3 3/4] describe: Store commit_names in a hash table by commit SHA1 Anders Kaseorg
2010-12-09  6:47                       ` [PATCH v3 4/4] describe: Delay looking up commits until searching for an inexact match Anders Kaseorg

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=20101206174723.GB6272@burratino \
    --to=jrnieder@gmail.com \
    --cc=andersk@ksplice.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=kirr@mns.spb.ru \
    --cc=szeder@ira.uka.de \
    --cc=trast@student.ethz.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