From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Jani Nikula <jani.nikula@linux.intel.com>,
Randy Dunlap <rdunlap@infradead.org>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH v1] docs: describe how to quickly build Linux
Date: Fri, 10 Feb 2023 08:55:04 -0500 [thread overview]
Message-ID: <20230210135504.jg7tmqhdmhfwdz5t@nitro.local> (raw)
In-Reply-To: <66fc12cd-65b6-0831-89a8-57636453883b@leemhuis.info>
On Fri, Feb 10, 2023 at 12:38:07PM +0100, Thorsten Leemhuis wrote:
> Downloading the sources using a full git clone
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> If downloading and storing a lot of data (~4,4 Gigabyte as of early
> 2023) is nothing that bothers you, instead of a shallow clone perform a
> full git clone instead.
As a minor segue, we know we can dramatically reduce the size of the stable
repo (and the stable clone.bundle) if we drop all branches and tags for old
EOL releases and move them to a separate repo (e.g. stable-eol.git).
I have suggested this in the past, but it's not a trivial change:
- it requires a fair amount of git work
- it may disrupt some of the build infra around the world still building EOL
kernels (for whatever reason)
In my preliminary tests, we easily dropped the size from 4GB to under 3GB.
-K
next prev parent reply other threads:[~2023-02-10 13:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 11:52 [PATCH v1] docs: describe how to quickly build Linux Thorsten Leemhuis
2023-02-01 12:42 ` Greg KH
2023-02-01 12:44 ` Greg KH
2023-02-01 13:22 ` Thorsten Leemhuis
2023-02-01 14:02 ` Greg KH
2023-02-02 11:15 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-02-02 14:27 ` Greg KH
2023-02-02 14:57 ` Thorsten Leemhuis
2023-02-02 15:08 ` Konstantin Ryabitsev
2023-02-02 15:36 ` Thorsten Leemhuis
2023-02-03 9:44 ` Jani Nikula
2023-02-03 9:52 ` Thorsten Leemhuis
2023-02-10 11:38 ` Thorsten Leemhuis
2023-02-10 13:55 ` Konstantin Ryabitsev [this message]
2023-02-25 9:17 ` Pavel Machek
2023-02-25 9:29 ` Thorsten Leemhuis
2023-02-25 13:34 ` Thorsten Leemhuis
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=20230210135504.jg7tmqhdmhfwdz5t@nitro.local \
--to=konstantin@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=rdunlap@infradead.org \
--cc=regressions@lists.linux.dev \
/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.