From: Andry <andry@inbox.ru>
To: "Đoàn Trần Công Danh" <congdanhqx@gmail.com>
Cc: Philip Oakley <philipoakley@iee.email>, git@vger.kernel.org
Subject: Re: Hash for a commit sourcetree beside to a commit hash
Date: Sat, 4 Feb 2023 07:50:23 +0300 [thread overview]
Message-ID: <1196589662.20230204075023@inbox.ru> (raw)
In-Reply-To: <Y90lBJ8b5nCUcLv2@danh.dev>
Hello Đoàn,
Friday, February 3, 2023, 6:15:16 PM, you wrote:
ĐTCD> On 2023-02-03 16:37:20+0300, Andry <andry@inbox.ru> wrote:
>> Hello Philip,
>> >> 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.
ĐTCD> You can limit the download with "git clone --filter=tree:0"
ĐTCD> which only fetch the commit but not any tree or file contents.
And what next? You still need to download something to see.
Better to start search in the remote anyway, because, for example, it is someone's else repository you don't want to download at all until you find something.
This is how it works in first place - you search something to start download, instead of to download at first to search something.
next prev parent reply other threads:[~2023-02-04 4:50 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
2023-02-03 15:15 ` Đoàn Trần Công Danh
2023-02-04 4:50 ` Andry [this message]
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=1196589662.20230204075023@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