From: "Eric Bénard" <eric@eukrea.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: Fetch time optimization (svn : gcc/eglibc - git : linux-yocto)
Date: Fri, 30 Mar 2012 18:17:52 +0200 [thread overview]
Message-ID: <20120330181752.080630b5@eb-e6520> (raw)
In-Reply-To: <1333123344.18082.94.camel@ted>
Le Fri, 30 Mar 2012 17:02:24 +0100,
Richard Purdie <richard.purdie@linuxfoundation.org> a écrit :
> The linux-yocto kernel recipe heavily uses the SCM to do things so
> whilst it does have a higher download cost, it as adds value and is
> ultimately a maintainers choice too.
>
OK now that I've given a closer look at the linux-yocto recipes &
bbclass I understand better why you need it in that recipe and that
this recipe is heavily based on git's features.
> So whilst I hear what you're saying, I don't think we can change
> anything other than the PREMIRROR...
>
then maybe for the new users testing OE, having PREMIRRORs set in the
default configuration would be a great thing so that they don't believe
OE is a big slow beast just because they have to wait hours for git or
svn to fetch sources.
Eric
next prev parent reply other threads:[~2012-03-30 16:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 20:53 Fetch time optimization (svn : gcc/eglibc - git : linux-yocto) Eric Bénard
2012-03-29 22:03 ` Richard Purdie
2012-03-30 1:03 ` Bruce Ashfield
2012-03-30 6:44 ` Samuel Stirtzel
2012-03-30 9:21 ` Paul Eggleton
2012-03-30 9:32 ` Richard Purdie
2012-03-30 10:07 ` Samuel Stirtzel
2012-03-30 10:45 ` Richard Purdie
2012-04-02 8:15 ` Samuel Stirtzel
2012-03-30 7:00 ` Martin Jansa
2012-03-30 10:06 ` Richard Purdie
2012-03-30 8:50 ` Eric Bénard
2012-03-30 15:12 ` Richard Purdie
2012-03-30 15:24 ` Eric Bénard
2012-03-30 15:49 ` Bruce Ashfield
2012-03-30 15:55 ` Eric Bénard
2012-03-30 16:02 ` Richard Purdie
2012-03-30 16:17 ` Eric Bénard [this message]
2012-03-30 17:33 ` Bruce Ashfield
2012-03-30 18:36 ` Eric Bénard
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=20120330181752.080630b5@eb-e6520 \
--to=eric@eukrea.com \
--cc=openembedded-core@lists.openembedded.org \
/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.