From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Why not perform a shallow clone?
Date: Wed, 24 Feb 2016 22:25:25 +0100 [thread overview]
Message-ID: <56CE1FC5.8090408@mind.be> (raw)
In-Reply-To: <CAF_dkJCgzJQE4i1DbDF_=eVgfEDJHDiwD-qRAjQe72ar+_=YBg@mail.gmail.com>
On 02/24/16 21:18, Patrick Doyle wrote:
> On Wed, Feb 24, 2016 at 2:50 PM, Patrick Doyle <wpdster@gmail.com> wrote:
[snip]
>> I suppose I could tell menuconfig that the (Atmel) kernel I am cloning
>> is available on github somehow and have the magic "fetch a sha1sum
>> from github" work. I'll go think about that for a bit.
>
> No, that doesn't seem to work either. linux.mk doesn't use $(call
> github). Oh well.
$(call github) is not really needed, you can just use the actual URL in your
config: https://github.com/<project>/<repo>/archive/<version>/<version>.tar.gz
Regards,
Arnout
>
> I suppose I could add support for that... does that seem useful to
> folks other than I?
>
> --wpd
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2016-02-24 21:25 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
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 [this message]
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=56CE1FC5.8090408@mind.be \
--to=arnout@mind.be \
--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.