git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 2/2] sha1_object_info: examine cached_object store too

From
Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
Date
Feb 5, 2011, 14:03 UTC
Message-ID
<1296914582-619-2-git-send-email-pclouds@gmail.com>
In-Reply-To
<1296914582-619-1-git-send-email-pclouds@gmail.com>

Cached object store was added in d66b37b (Add pretend_sha1_file() interface. - 2007-02-04) as a way to temporarily inject some objects to object store.

But only read_sha1_file() knows about this store. While it will return an object from this store, sha1_object_info() will happily say "object not found".

Teach sha1_object_info() about the cached store for consistency.
Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
---
 "git mktree" does not accept empty tree as it should do because of this.
 sha1_file.c |    8 ++++++++
 1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/sha1_file.c b/sha1_file.c
index 9fd7e16..0b830c8 100644
--- a/sha1_file.c
+++ b/sha1_file.c
@@ -2020,9 +2020,17 @@ static int sha1_loose_object_info(const unsigned char *sha1, unsigned long *size
 
 int sha1_object_info(const unsigned char *sha1, unsigned long *sizep)
 {
+	struct cached_object *co;
 	struct pack_entry e;
 	int status;
 
+	co = find_cached_object(sha1);
+	if (co) {
+		if (sizep)
+			*sizep = co->size;
+		return co->type;
+	}
+
 	if (!find_pack_entry(sha1, &e)) {
 		/* Most likely it's a loose object. */
 		status = sha1_loose_object_info(sha1, sizep);
-- 
1.7.3.4.878.g439c7
Previous: Nguyễn Thái Ngọc Duy
Message 2 of 2 in “sha1_file.c: move find_cached_object up so sha1_object_info can use it”
  1. 1/2 sha1_file.c: move find_cached_object up so sha1_object_info can use itNguyễn Thái Ngọc Duy, Feb 5, 2011
  2. 2/2 sha1_object_info: examine cached_object store tooNguyễn Thái Ngọc Duy, Feb 5, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.