From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH v2 1/3] meta-systemd: Move ntp recipes to 'meta-networking' sublayer
Date: Wed, 31 Oct 2012 12:38:24 +0000 [thread overview]
Message-ID: <1351687105.13864.110.camel@phil-desktop> (raw)
In-Reply-To: <CAP9ODKq=8EwPNT3wqGAnVuweEj4wwYNGKLhhzHUaP0H-gRSnQg@mail.gmail.com>
On Wed, 2012-10-31 at 10:29 -0200, Otavio Salvador wrote:
> Well, I cannot ask for a pool zone for OE or Yocto; it'd be good but
> it is not yet done and I prefer to have it merged and changed once it
> happens.
The obvious problem with that approach is that "it" may never happen
(especially if you're relying on some as-yet-unidentified third party to
do the work) and, even if it does, arbitrarily many people might ship
the broken configuration in the meantime. Merging a change that we know
is wrong seems like a bad plan.
p.
next prev parent reply other threads:[~2012-10-31 12:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 11:08 [meta-oe][PATCH v2 1/3] meta-systemd: Move ntp recipes to 'meta-networking' sublayer Otavio Salvador
2012-10-31 11:08 ` [meta-oe][PATCH v2 2/3] meta-systemd: meta-networking: ntp: Update bbappend to 4.2.6p5 Otavio Salvador
2012-11-22 6:22 ` Anders Darander
2012-11-22 10:35 ` Paul Eggleton
2012-10-31 11:08 ` [meta-oe][PATCH v2 3/3] freerdp: Bump SRCREV to 1.0.2 snapshot of 2012-10-30 Otavio Salvador
2012-10-31 11:43 ` [meta-oe][PATCH v2 1/3] meta-systemd: Move ntp recipes to 'meta-networking' sublayer Martin Ertsås
2012-10-31 11:52 ` Anders Darander
2012-10-31 12:02 ` Otavio Salvador
2012-10-31 12:11 ` Phil Blundell
2012-10-31 12:09 ` Martin Ertsås
2012-10-31 12:19 ` Phil Blundell
2012-10-31 12:29 ` Otavio Salvador
2012-10-31 12:38 ` Phil Blundell [this message]
2012-10-31 12:40 ` Otavio Salvador
2012-10-31 12:45 ` Phil Blundell
2012-10-31 12:52 ` Otavio Salvador
2012-10-31 12:32 ` Burton, Ross
2012-10-31 12:15 ` Otavio Salvador
2012-10-31 12:22 ` Phil Blundell
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=1351687105.13864.110.camel@phil-desktop \
--to=philb@gnu.org \
--cc=openembedded-devel@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.