From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] pkg-download: Make a shallow clone for git downloads
Date: Sun, 04 Nov 2012 00:57:55 +0100 [thread overview]
Message-ID: <87hap6w870.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1351732866-29730-1-git-send-email-arnout@mind.be> (Arnout Vandecappelle's message of "Thu, 1 Nov 2012 02:21:05 +0100")
>>>>> "Arnout" == Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> writes:
Arnout> When downloading from git, we clone the whole repository and then only
Arnout> use the latest commit. That's a lot of redundant stuff. So instead,
Arnout> make a shallow clone. Unfortunately that's only possible when
Arnout> downloading a branch or tag, so fall back to the old method if git gives
Arnout> an error.
Arnout> This speeds up the cloning of a linux git from more than 2 hours to
Arnout> 20 minutes on a 200KB/s link).
And just think what difference it will make on the hotel Grumps
connection ;)
Committed, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2012-11-03 23:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 1:21 [Buildroot] [PATCH] pkg-download: Make a shallow clone for git downloads Arnout Vandecappelle
2012-11-03 18:09 ` Luca Ceresoli
2012-11-03 23:57 ` Peter Korsgaard [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=87hap6w870.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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