From: Junio C Hamano <gitster@pobox.com>
To: Yubin Ruan <ablacktshirt@gmail.com>
Cc: Philip Oakley <philipoakley@iee.org>, git@vger.kernel.org
Subject: Re: Meaning of two commit-ish hash in git diff
Date: Wed, 01 Nov 2017 11:48:02 +0900 [thread overview]
Message-ID: <xmqqfu9yww7x.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <127f7748-4b5d-f6be-2c64-fa4ee079b871@gmail.com> (Yubin Ruan's message of "Wed, 1 Nov 2017 09:07:20 +0800")
Yubin Ruan <ablacktshirt@gmail.com> writes:
>>> 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 ;-)
prev parent reply other threads:[~2017-11-01 2:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 3:24 Meaning of two commit-ish hash in git diff Yubin Ruan
2017-10-31 4:28 ` Junio C Hamano
2017-11-01 0:27 ` Philip Oakley
2017-11-01 1:07 ` Yubin Ruan
2017-11-01 2:48 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqfu9yww7x.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=ablacktshirt@gmail.com \
--cc=git@vger.kernel.org \
--cc=philipoakley@iee.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox