From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Caleb Gray <hey@calebgray.com>, git@vger.kernel.org
Subject: Re: Add a "Flattened Cache" to `git --clone`?
Date: Thu, 14 May 2020 17:05:01 -0400 [thread overview]
Message-ID: <20200514210501.GY1596452@mit.edu> (raw)
In-Reply-To: <20200514203326.2aqxolq5u75jx64q@chatter.i7.local>
On Thu, May 14, 2020 at 04:33:26PM -0400, Konstantin Ryabitsev wrote:
> > Assuming my idea doesn't contradict other best practices or standards
> > already in place, I'd like to transform the typical `git clone` flow
> > from:
> >
> > Cloning into 'linux'...
> > remote: Enumerating objects: 4154, done.
> > remote: Counting objects: 100% (4154/4154), done.
> > remote: Compressing objects: 100% (2535/2535), done.
> > remote: Total 7344127 (delta 2564), reused 2167 (delta 1612),
> > pack-reused 7339973
> > Receiving objects: 100% (7344127/7344127), 1.22 GiB | 8.51 MiB/s, done.
> > Resolving deltas: 100% (6180880/6180880), done.
> >
> > To subsequent clones (until cache invalidated) using the "flattened
> > cache" version (presumably built while fulfilling the first clone
> > request above):
> >
> > Cloning into 'linux'...
> > Receiving cache: 100% (7344127/7344127), 1.22 GiB | 8.51 MiB/s, done.
>
> I don't think it's a common workflow for someone to repeatedly clone
> linux.git. Automated processes like CI would be doing it, but they tend
> to blow away the local disk between jobs, so they are unlikely to
> benefit from any native git local cache for something like this (in
> fact, we recommend that people use clone.bundle files for their CI
> needs, as described here:
> https://www.kernel.org/best-way-to-do-linux-clones-for-your-ci.html).
If the goal is a git local cache, we have this today. I'm not sure
this is what Caleb was asking for, though:
git clone --bare https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git base
git clone --reference base https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git ext4
- Ted
next prev parent reply other threads:[~2020-05-14 21:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 14:34 Add a "Flattened Cache" to `git --clone`? Caleb Gray
2020-05-14 20:33 ` Konstantin Ryabitsev
2020-05-14 20:54 ` Bryan Turner
2020-05-14 21:05 ` Theodore Y. Ts'o [this message]
2020-05-14 21:09 ` Eric Sunshine
2020-05-14 21:10 ` Konstantin Ryabitsev
2020-05-14 21:23 ` Junio C Hamano
2020-05-14 21:44 ` Konstantin Ryabitsev
2020-05-15 21:42 ` Eric Wong
2020-05-17 22:12 ` Konstantin Ryabitsev
[not found] ` <1061511589863147@mail.yandex.ru>
2020-05-25 14:02 ` Caleb Gray
2020-05-14 21:33 ` Caleb Gray
2020-05-14 21:56 ` Junio C Hamano
2020-05-14 22:04 ` Caleb Gray
2020-05-14 22:30 ` Junio C Hamano
2020-05-14 22:44 ` Bryan Turner
2020-05-14 21:19 ` Junio C Hamano
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=20200514210501.GY1596452@mit.edu \
--to=tytso@mit.edu \
--cc=git@vger.kernel.org \
--cc=hey@calebgray.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.