All of lore.kernel.org
 help / color / mirror / Atom feed
From: McClintock Matthew-B29882 <B29882@freescale.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: McClintock Matthew-B29882 <B29882@freescale.com>
Subject: Re: bitbake.conf: Add git-native to ASSUME_PROVIDED
Date: Tue, 10 Jul 2012 16:11:50 +0000	[thread overview]
Message-ID: <CAEsOVNfmMP0kjyA==CaSwYb4SBpyaD+dBmi8CAL+Qy=Ya=HtSQ@mail.gmail.com> (raw)
In-Reply-To: <1341935849.1294.2.camel@ted>

On Tue, Jul 10, 2012 at 10:57 AM, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
> Every time we put an if statement in like this, it basically means we
> should double the amount of QA, one for one path and one for the other.
>
> So whilst I've wondered about it, do we really need to do something like
> this?

I don't think we need it, it just has the possibility of improving the
initial user experience. What's the QA difference in testing all the
various differences in git (or whatever) on the distros we intend to
support? In a way ASSUME_PROVIDED += "git" more than doubled the QA ;)

-M



  parent reply	other threads:[~2012-07-10 16:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-10 13:32 bitbake.conf: Add git-native to ASSUME_PROVIDED Richard Purdie
2012-07-10 14:02 ` Robert P. J. Day
2012-07-10 14:09   ` Richard Purdie
2012-07-10 14:14     ` Robert P. J. Day
2012-07-10 15:00 ` McClintock Matthew-B29882
2012-07-10 15:57   ` Richard Purdie
2012-07-10 16:06     ` Burton, Ross
2012-07-10 16:11     ` McClintock Matthew-B29882 [this message]
2012-07-10 18:35     ` Robert P. J. Day
2012-07-10 18:52       ` Khem Raj
2012-07-10 19:23         ` Richard Purdie
2012-07-10 19:58         ` Robert P. J. Day
2012-07-16 22:06   ` Colin Walters
2012-07-11 12:23 ` Enrico Scholz
2012-07-11 16:19   ` Richard Purdie

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='CAEsOVNfmMP0kjyA==CaSwYb4SBpyaD+dBmi8CAL+Qy=Ya=HtSQ@mail.gmail.com' \
    --to=b29882@freescale.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.