From: Collin Funk <collin.funk1@gmail.com>
To: Daniel Kiper via Grub-devel <grub-devel@gnu.org>
Cc: Andrew Hamilton <adhamilt@gmail.com>,
Daniel Kiper <daniel.kiper@oracle.com>,
ghetman@gmail.com
Subject: Re: [PATCH v2 1/1] bootstrap: Ensure shallow GNULIB clone Works on Newer GIT
Date: Mon, 25 Aug 2025 08:15:37 -0700 [thread overview]
Message-ID: <87o6s3h1pi.fsf@gmail.com> (raw)
In-Reply-To: <aKx8rzvs6LU9VIHd@tomti.i.net-space.pl>
Daniel Kiper via Grub-devel <grub-devel@gnu.org> writes:
> On Sun, Aug 24, 2025 at 08:38:41PM -0500, Andrew Hamilton wrote:
>> Update the bootstrap script to be compatible with newer versions
>> of GIT that changed the git clone -h output from containing:
>> "--depth"
>> to:
>> "--[no-]depth"
>> This bootstrap script is pulled the latest GNULIB version
>> from GNULIB GIT, commit 9a1a6385
>> This change avoids a full clone on GNULIB, saving
>> something like 50 MB.
>>
>> Fixes: https://savannah.gnu.org/bugs/?66357
>>
>> Signed-off-by: Andrew Hamilton <adhamilt@gmail.com>
>
> OK, let's take some risk and try it...
>
> Reviewed-by: Daniel Kiper <daniel.kiper@oracle.com>
FYI, you can use the GNULIB_SRCDIR enviornment variable to save
time and bandwidth. Since I am a Gnulib developer and commit to various
projects that use Gnulib I have the following in my ~/.profile:
export GNULIB_SRCDIR="$HOME/.local/src/gnulib"
Collin
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
prev parent reply other threads:[~2025-08-25 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 1:38 [PATCH v2 0/1] bootstrap: Reduce GNULIB Size on Newer GIT Andrew Hamilton
2025-08-25 1:38 ` [PATCH v2 1/1] bootstrap: Ensure shallow GNULIB clone Works " Andrew Hamilton
2025-08-25 15:09 ` Daniel Kiper via Grub-devel
2025-08-25 15:15 ` Collin Funk [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=87o6s3h1pi.fsf@gmail.com \
--to=collin.funk1@gmail.com \
--cc=adhamilt@gmail.com \
--cc=daniel.kiper@oracle.com \
--cc=ghetman@gmail.com \
--cc=grub-devel@gnu.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;
as well as URLs for NNTP newsgroup(s).