All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] Fetching kernel via git
Date: Mon, 01 Feb 2010 09:25:53 +0000	[thread overview]
Message-ID: <4B669E21.4030303@carallon.com> (raw)
In-Reply-To: <66a1.4b66259d.a7107@getafix.xdna.net>

On 01/02/2010 00:51, Cameron Hutchison wrote:
> Is there some way to configure buildroot to fetch the kernel sources
> via git?
>    

Patches have been posted on the mailing list before. See 
http://lists.busybox.net/pipermail/buildroot/2010-January/031499.html 
for most recent.

Will try to clean up my patch and submit it shortly.

Will
> I am currently downloading my third complete kernel source tree for
> 2.6.32.7, previously having downloaded 2.6.23.3 and 2.6.31.6.
>
> I keep a git repository with a clone of Linus's public tree and the
> stable trees, so it would save greatly on bandwidth and time if
> buildroot could clone the kernel from that local repository instead of
> downloading a source tarball every time the extraversion bumps up a
> version.
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>    

-- 
------------------------------------------------------------------------
Will Wagner                                     will_wagner at carallon.com
Development Manager                      Office Tel: +44 (0)20 7371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------

      reply	other threads:[~2010-02-01  9:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-01  0:51 [Buildroot] Fetching kernel via git Cameron Hutchison
2010-02-01  9:25 ` William Wagner [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=4B669E21.4030303@carallon.com \
    --to=will_wagner@carallon.com \
    --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.