From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel <openembedded-devel@openembedded.org>
Subject: Stable Branch
Date: Wed, 14 May 2008 15:32:23 +0100 [thread overview]
Message-ID: <1210775543.7097.29.camel@localhost.localdomain> (raw)
Just to make things clear the stable branch has the full support of the
OE core team. We're aware some members of the community are vocal in
their dislike of the way its being run but these do not reflect the
views of the majority. To clarify the position with the bugzilla, it
remains the place to submit and track OE bugs, be them in .dev, stable
or any other branch. If any branch has a submission procedure for
changes in addition to that, that is up to the maintainers of the
branch.
We'd like to ask people to work together to make the stable branch a
success and make best use of our limited resources.
--
The OE Core Team
next reply other threads:[~2008-05-14 14:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 14:32 Richard Purdie [this message]
2008-05-14 16:44 ` Stable Branch Rolf Leggewie
2008-05-14 18:37 ` markgross
2008-05-18 23:56 ` mark gross
2009-03-12 22:00 ` Bernhard Guillon
-- strict thread matches above, loose matches on Subject: below --
2009-03-12 21:11 Shane Dixon
2009-03-12 21:43 ` Philip Balister
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=1210775543.7097.29.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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