From: Andry <andry@inbox.ru>
To: "Philip Oakley" <philipoakley@iee.email>,
"Đoàn Trần Công Danh" <congdanhqx@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Hash for a commit sourcetree beside to a commit hash
Date: Fri, 3 Feb 2023 16:37:20 +0300 [thread overview]
Message-ID: <1309893232.20230203163720@inbox.ru> (raw)
In-Reply-To: <22255406-42da-9ac3-4783-11a035877a3c@iee.email>
Hello Philip,
Friday, February 3, 2023, 2:11:19 PM, you wrote:
PO> On 03/02/2023 02:21, Andry wrote:
>> Đoàn,
>> Friday, February 3, 2023, 5:01:09 AM, you wrote:
>> ĐTCD> git rev-list <a-commit-tish> |
>> ĐTCD> while read commit; do
>> ĐTCD> if test $(git rev-parse $commit^{tree}) = $hash; then
>> ĐTCD> echo $commit
>> ĐTCD> break
>> ĐTCD> fi
>> ĐTCD> done
>>
>> Nice, but I can not apply this over a git hub or a web interface without a clone.
PO> As a 'Distributed'-VCS, cloning the repository would be the de-facto
PO> normal approach, otherwise you have re-invented centralised VCS ;-)
Cloning repository is a heavy operation by downloading everything instead of search a single commit.
And searching at the remote does not make it a central.
PO> Alternatively, you could approach the server (hub/web interface)
PO> provider to see if they are willing to provide that level of search
PO> interface.
The GitHub already provides that in the search field. Just input a hash and see what happens.
next prev parent reply other threads:[~2023-02-03 13:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 1:28 Hash for a commit sourcetree beside to a commit hash Andry
2023-02-03 2:01 ` Đoàn Trần Công Danh
2023-02-03 2:21 ` Andry
2023-02-03 11:11 ` Philip Oakley
2023-02-03 13:37 ` Andry [this message]
2023-02-03 15:15 ` Đoàn Trần Công Danh
2023-02-04 4:50 ` Andry
2023-02-03 22:39 ` Philip Oakley
2023-02-05 1:41 ` Andry
2023-02-12 13:27 ` Andry
2023-02-26 9:37 ` Andry
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=1309893232.20230203163720@inbox.ru \
--to=andry@inbox.ru \
--cc=congdanhqx@gmail.com \
--cc=git@vger.kernel.org \
--cc=philipoakley@iee.email \
/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