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

Re: blameview and file contents

From
Shawn O. Pearce <spearce@spearce.org>
Date
Jan 30, 2007, 07:29 UTC
Message-ID
<20070130072910.GB32640@spearce.org>
In-Reply-To
<cc723f590701292322q7365f99bg3b7c76834f6fbad8@mail.gmail.com>
Aneesh Kumar <aneesh.kumar@gmail.com> wrote:
> See i said that there should be a simple way. Can we get this
> documented in git-cat-file man page

Well, this isn't the git-cat-file man page, but we do suggest people use `git show HEAD:foo.c` to get foo.c from HEAD in an interactive setting. The git-show manpage refers people to git-rev-parse, which has the following:

	* A suffix ':' followed by a path; this names the blob or tree
	  at the given path in the tree-ish object named by the part
	  before the colon.

In a non-interactive case, well, that's what git-cat-file is for. And <object> typically is meant to mean what git-rev-parse will parse...

But if you submit a documentation update to git-cat-file's manpage that points off to the same section of git-rev-parse, folks may appreciate it. :-)

-- 
Shawn.
Previous: Aneesh KumarNext: Junio C Hamano
Message 4 of 5 in “blameview and file contents”
  1. Aneesh KumarJan 30, 2007
  2. Shawn O. PearceJan 30, 2007
  3. Aneesh KumarJan 30, 2007
  4. Shawn O. PearceJan 30, 2007
  5. Junio C HamanoJan 30, 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.