From: "Eric Bénard" <eric@eukrea.com>
To: clarson@kergoth.com
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH][for-danny] guile: remove from meta-oe, there is newer version in oe-core
Date: Fri, 5 Apr 2013 22:13:05 +0200 [thread overview]
Message-ID: <20130405221305.6a7ae319@e6520eb> (raw)
In-Reply-To: <CABcZANkitD_S70HFXiM+xnC73avzC-2LDjRTcezwVMe1VcW+ow@mail.gmail.com>
Hi Christopher,
Le Fri, 5 Apr 2013 10:02:22 -0700,
Chris Larson <clarson@kergoth.com> a écrit :
> I'm a bit confused about why this went in. danny is a stable branch, and
> this is clearly not a bugfix. Did the existence of this recipe actually
> cause a problem? This just caused a temporary build break for us due to
> bbappending to a removed recipe. What exactly is the policy for meta-oe's
> danny branch, if it's not "bugfixes only"?
I usually apply patches to danny-next and wait at least one week to get
feedback before pushing to danny (and usually I try to do that on a
friday).
So if you want to prevent this kind of problem for the future, you may
be able to configure one of your autobuilders to build your
projects using danny-next's branch so that you get the error before the
patches are pushed to danny.
Best regards,
Eric
next prev parent reply other threads:[~2013-04-05 20:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 9:48 [PATCH][for-danny] guile: remove from meta-oe, there is newer version in oe-core Ross Burton
2013-03-21 13:07 ` Eric Bénard
2013-04-05 17:02 ` Chris Larson
2013-04-05 17:13 ` Burton, Ross
2013-04-05 17:40 ` Chris Larson
2013-04-05 19:37 ` Burton, Ross
2013-04-05 20:13 ` Eric Bénard [this message]
2013-04-05 22:09 ` Chris Larson
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=20130405221305.6a7ae319@e6520eb \
--to=eric@eukrea.com \
--cc=clarson@kergoth.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox