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

[GNU bug Tracking System]

Your message dated Sun, 22 Mar 2020 16:48:10 -0400
with message-id <address@hidden>
and subject line Re: bug#30428: guix git-fetch doesn't specify "--depth 1" - 
git clone clones a lot without any use
has caused the debbugs.gnu.org bug report #30428,
regarding guix git-fetch doesn't specify "--depth 1" - git clone clones a lot 
without any use
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden.)


-- 
30428: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=30428
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> guix git-fetch doesn't specify "--depth 1" - git clone clones a lot without any use
>
>
>
>
> Date: 
>
> Mon, 12 Feb 2018 01:16:41 +0100
>
>
>
>
> 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?
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#30428: guix git-fetch doesn't specify "--depth 1" - git clone clones a lot without any use
>
>
>
>
> Date: 
>
> Sun, 22 Mar 2020 16:48:10 -0400
>
>
>
>
> 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 329dabe13bf98b899b907b45565434c5140804f5. Closing.
>
>
> --- End Message ---