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

Re: [PATCH] get_tree_entry: map blank requested entry to tree root

From
Jeff King <peff@peff.net>
Date
Jan 10, 2007, 00:46 UTC
Message-ID
<20070110004633.GA14345@coredump.intra.peff.net>
In-Reply-To
<7vk5zviwxa.fsf@assigned-by-dhcp.cox.net>
On Tue, Jan 09, 2007 at 03:48:33PM -0800, Junio C Hamano wrote:
> Makes sense, although I somewhat worry about changing the
> behaviour and potentially breaking the expectation of callers
> of get_tree_entry() other than "git show".
Previously, trying to get an empty name would always return -1. Most of
the users besides sha1_name are getting the paths by enumerating the
index or an existing tree, so they will never be blank. The exceptions
are:
 - git-blame ''; this fails in both the root and a subdir (though with
   different errors); behavior is unchanged with my patch
 - git-archive feeds the 'prefix' variable to get_tree_entry; it works
   fine in the root with or without the patch. I seem to be getting an
   error, with or without my patch, when doing a git-archive from a
   subdirectory:
     $ git-archive --format=tar origin >/dev/null
     $ cd Documentation
     $ git-archive --format=tar origin >/dev/null
     fatal: cannot read c87c61af00c6d2cd7212240e260809000000aaab
   but I haven't been able to track it down further. It's clearly
   unrelated to my patch, though.

The main difference is that looking up a ref through sha1_name used to fail to match 'HEAD:'; now it does. So if you were trying to match a file 'HEAD:' without using '--', you're out of luck.

-Peff
Previous: Junio C HamanoNext: Junio C Hamano
Message 4 of 7 in “get_tree_entry: map blank requested entry to tree root”
  1. get_tree_entry: map blank requested entry to tree rootJeff King, Jan 9, 2007
  2. Johannes SchindelinJan 9, 2007
  3. Junio C HamanoJan 9, 2007
  4. Jeff KingJan 10, 2007
  5. Junio C HamanoJan 10, 2007
  6. Jeff KingJan 10, 2007
  7. Junio C HamanoJan 10, 2007

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.