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

Re: Meaning of two commit-ish hash in git diff

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 1, 2017, 02:48 UTC
Message-ID
<xmqqfu9yww7x.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<127f7748-4b5d-f6be-2c64-fa4ee079b871@gmail.com>
Yubin Ruan <ablacktshirt@gmail.com> writes:
Show 13 quoted lines
>>> IOW, if you have the contents of the blob whose object name is
>>> f8886b4, by applying this patch, you will get a blob whose object
>>> name is a1c96df.
>>>
>>> The information is used by "git am -3" when the patch does not apply
>>> cleanly to fall back to the 3-way merge.
>> 
>> The ability to 'git describe` those blob object IDs is currently the subject of a patch series
>> https://public-inbox.org/git/20171031211852.13001-1-sbeller@google.com/
>> 
>> Maybe see if would have helped ;-)
>
> What would be other use case of the blob object / blob name ?

Perhaps start from "git cat-file blob $name". And follow the path your imagination leads you to ;-)

Previous: Yubin Ruan
Message 5 of 5 in “Meaning of two commit-ish hash in git diff”
  1. Yubin RuanOct 31, 2017
  2. Junio C HamanoOct 31, 2017
  3. Philip OakleyNov 1, 2017
  4. Yubin RuanNov 1, 2017
  5. Junio C HamanoNov 1, 2017

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.