From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] Why not perform a shallow clone?
Date: Wed, 24 Feb 2016 21:36:49 +0200 [thread overview]
Message-ID: <20160224193649.GL2225@tarshish> (raw)
In-Reply-To: <CAF_dkJA0tBn_6x-sBwqF6Hb4x4+Pp3vM+e+rndm24kJe_y6pVg@mail.gmail.com>
Hi Patrick,
On Wed, Feb 24, 2016 at 02:30:58PM -0500, Patrick Doyle wrote:
> So I'm sitting here watching my buildroot make do a complete clone of
> the Linux kernel, where I have told it that I want a specific sha1
> commit and I started wondering...
>
> Why not do a shallow clone?
>
> Has it been tried? Is it a bad idea?
Quoting the support/download/git script:
# Try a shallow clone, since it is faster than a full clone - but that only
# works if the version is a ref (tag or branch). Before trying to do a shallow
# clone we check if ${cset} is in the list provided by git ls-remote. If not
# we fall back on a full clone.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2016-02-24 19:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 19:30 [Buildroot] Why not perform a shallow clone? Patrick Doyle
2016-02-24 19:36 ` Baruch Siach [this message]
2016-02-24 19:41 ` Samuel Martin
2016-02-24 19:50 ` Patrick Doyle
2016-02-24 20:18 ` Patrick Doyle
2016-02-24 21:25 ` Arnout Vandecappelle
2016-02-24 21:35 ` Patrick Doyle
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=20160224193649.GL2225@tarshish \
--to=baruch@tkos.co.il \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.