bug#30428: guix git-fetch doesn't specify "--depth 1" - git clone clones a lot without any use

On Mon, Feb 12, 2018 at 01:16:41AM +0100, Danny Milosavljevic wrote: > git-fetch doesn't allow specifying "--depth 1". > > That means the repo clones are needlessly large. > > Since in packages we only need one specific commit anyhow why do we fetch > all the other commits? This was fixed in

bug#30428: guix git-fetch doesn't specify "--depth 1" - git clone clones a lot without any use

Hi Danny, Danny Milosavljevic skribis: > It's already much nicer just to try the shallow commit checkout and fall back > to the current way if it doesn't work - and it's low risk. Oh right, I hadn’t groked that this is what your patch does. In that case I’m all for it,

bug#30428: guix git-fetch doesn't specify "--depth 1" - git clone clones a lot without any use

Hi Ludo, On Wed, 14 Feb 2018 14:58:55 +0100 l...@gnu.org (Ludovic Courtès) wrote: > I think it’s a great idea. FWIW, Andy proposed something along these > lines, but the idea was to use shallow clones for tags only because in > other cases it might not work (?): > >

bug#30428: guix git-fetch doesn't specify "--depth 1" - git clone clones a lot without any use

On Tue, Feb 13, 2018 at 06:08:58PM +0100, Marius Bakke wrote: > > > On February 13, 2018 3:22:58 PM GMT+01:00, Leo Famulari > wrote: > >On Mon, Feb 12, 2018 at 11:59:50PM +0100, Danny Milosavljevic wrote: > >> Leo Famulari wrote: > >> > >> > I think

bug#30428: guix git-fetch doesn't specify "--depth 1" - git clone clones a lot without any use

On February 13, 2018 3:22:58 PM GMT+01:00, Leo Famulari wrote: >On Mon, Feb 12, 2018 at 11:59:50PM +0100, Danny Milosavljevic wrote: >> Leo Famulari wrote: >> >> > I think it's worth adding, but as an option, because there are Git >> > server

bug#30428: guix git-fetch doesn't specify "--depth 1" - git clone clones a lot without any use

On Mon, Feb 12, 2018 at 11:59:50PM +0100, Danny Milosavljevic wrote: > Leo Famulari wrote: > > > I think it's worth adding, but as an option, because there are Git > > server implementations, like JGit, that don't support shallow cloning. > > Thanks for that! I didn't

bug#30428: guix git-fetch doesn't specify "--depth 1" - git clone clones a lot without any use

I think Google uses JGit for their public facing Git servers, but I'm not sure. On February 12, 2018 5:59:50 PM EST, Danny Milosavljevic wrote: >Hi Leo, > >On Mon, 12 Feb 2018 10:09:39 -0500 >Leo Famulari wrote: > >> I think it's worth adding, but as

bug#30428: guix git-fetch doesn't specify "--depth 1" - git clone clones a lot without any use

Hi Leo, On Mon, 12 Feb 2018 10:09:39 -0500 Leo Famulari wrote: > I think it's worth adding, but as an option, because there are Git > server implementations, like JGit, that don't support shallow cloning. Thanks for that! I didn't consider that before... Possible patch

bug#30428: guix git-fetch doesn't specify "--depth 1" - git clone clones a lot without any use

git-fetch doesn't allow specifying "--depth 1". That means the repo clones are needlessly large. Since in packages we only need one specific commit anyhow why do we fetch all the other commits?