Re: [PATCH] bootstrap: When a commit hash is specified, do a shallow fetch if possible

2022-01-05 Thread Bruno Haible
Hello Glenn, > I posted a v2 of the patch back in October with the requested comment > above. I'm guessing it got missed. If you still want me to repost the > v2 patch please let me know. > > [1] https://lists.gnu.org/archive/html/bug-gnulib/2021-10/msg00073.html Indeed, I missed it. Sorry

Re: [PATCH] bootstrap: When a commit hash is specified, do a shallow fetch if possible

2022-01-05 Thread Glenn Washburn
Hi Bruno, On Wed, 05 Jan 2022 11:50:13 +0100 Bruno Haible wrote: > Hi Glenn, > > In this thread, on 2021-10-24 I replied: > > > I'm thinking of replacing the current comment with > > > something along the lines of: > > > > > > Git does not support cloning by commit hash. So attempt a

Re: [PATCH] bootstrap: When a commit hash is specified, do a shallow fetch if possible

2022-01-05 Thread Bruno Haible
Hi Glenn, In this thread, on 2021-10-24 I replied: > > I'm thinking of replacing the current comment with > > something along the lines of: > > > > Git does not support cloning by commit hash. So attempt a shallow > > fetch by commit hash to minimize the amount of data downloaded and > >

Re: [PATCH] bootstrap: When a commit hash is specified, do a shallow fetch if possible

2021-10-27 Thread Simon Josefsson via Gnulib discussion list
Bruno Haible writes: >> > Also, I would expect that the GNULIB_REVISION environment variable is not >> > so frequently used, and that the more frequent use is with git submodules. >> > Is it possible to apply the same trick to the git submodules case? Or does >> > the use of submodules always

Re: [PATCH] bootstrap: When a commit hash is specified, do a shallow fetch if possible

2021-10-24 Thread Bruno Haible
Hi Glenn, > I'm thinking of replacing the current comment with > something along the lines of: > > Git does not support cloning by commit hash. So attempt a shallow > fetch by commit hash to minimize the amount of data downloaded and > changes needed to be processed, which can drastically

Re: [PATCH] bootstrap: When a commit hash is specified, do a shallow fetch if possible

2021-10-24 Thread Glenn Washburn
Hi Bruno, On Sat, 23 Oct 2021 00:20:32 +0200 Bruno Haible wrote: > Hi Glenn, > > > The gnulib sources are large but more importantly have lots of changes. So > > initial checkout of the repository can take a long time when network or > > cpu resources are limited. The later is especially acute

Re: [PATCH] bootstrap: When a commit hash is specified, do a shallow fetch if possible

2021-10-22 Thread Bruno Haible
Hi Glenn, > The gnulib sources are large but more importantly have lots of changes. So > initial checkout of the repository can take a long time when network or > cpu resources are limited. The later is especially acute in a non-KVM QEMU > virtual machine (which can take 40+ minutes compared to

Re: [PATCH] bootstrap: When a commit hash is specified, do a shallow fetch if possible

2021-10-22 Thread Glenn Washburn
On Thu, 21 Oct 2021 13:31:31 -0500 Glenn Washburn wrote: > The gnulib sources are large but more importantly have lots of changes. So > initial checkout of the repository can take a long time when network or > cpu resources are limited. The later is especially acute in a non-KVM QEMU > virtual

[PATCH] bootstrap: When a commit hash is specified, do a shallow fetch if possible

2021-10-21 Thread Glenn Washburn
The gnulib sources are large but more importantly have lots of changes. So initial checkout of the repository can take a long time when network or cpu resources are limited. The later is especially acute in a non-KVM QEMU virtual machine (which can take 40+ minutes compared to <30 seconds with