From: "Robert P. J. Day" <rpjday@crashcourse.ca>
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 15:58:20 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1207101557080.3817@oneiric> (raw)
In-Reply-To: <CAMKF1sqrf_hPLpYhY-sJzVBx5pHrV8_VWF9+6OjzKo5+Qqa+qQ@mail.gmail.com>
On Tue, 10 Jul 2012, Khem Raj wrote:
> On Tue, Jul 10, 2012 at 11:35 AM, Robert P. J. Day
> <rpjday@crashcourse.ca> wrote:
> >
> > my opinion, which is mine, is to add a script someone can run that
> > tells them what appears to be safe to override from their current
> > distro. that way, it's entirely optional and the developer deals with
> > the output at their own risk.
>
> who determines the safeness ? thats what double QA RP mentioned is
there's no *guarantee* of safeness, just an advisory based on
nothing more than the version number. user makes their own decision
and, if it breaks, they get to keep all the pieces.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2012-07-10 20:09 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
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 [this message]
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=alpine.DEB.2.02.1207101557080.3817@oneiric \
--to=rpjday@crashcourse.ca \
--cc=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.