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

Re: Git tree/blob and corresponding commit

From
BDBryan Donlan <bdonlan@gmail.com>
Date
Aug 15, 2008, 19:39 UTC
Message-ID
<3e8340490808151239u4572f5e4l11c16e0225509224@mail.gmail.com>
In-Reply-To
<48A43AEC.6000904@obry.net>
On Thu, Aug 14, 2008 at 10:02 AM, Pascal Obry <pascal@obry.net> wrote:
Show 9 quoted lines
> Jonathan,
>
>> but I actually meant
>>
>> <http://thread.gmane.org/gmane.comp.version-control.git/44750/focus=44849>.
>> Anyway, the whole thread is interesting.  Sorry for the noise.
>
> Thanks, I had a look. This is indeed giving some procedure... I was hopping
> for something faster (git rev-list takes some time!).

It's not really meant to be a common case; if the same file is created under different names by different commits that aren't ancestors of each other, then it's unclear which should be reported. As such, there's no index or other such thing to quickly find the commits corresponding to a blob, so you just have to walk the entire history.

Previous: Pascal Obry
Message 5 of 5 in “Git tree/blob and corresponding commit”
  1. Pascal ObryAug 10, 2008
  2. Jonathan NiederAug 10, 2008
  3. Jonathan NiederAug 10, 2008
  4. Pascal ObryAug 14, 2008
  5. Bryan DonlanAug 15, 2008

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.