From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OpenEmbedded Development mailing list
<openembedded-devel@lists.openembedded.org>
Subject: trying to get newest bitbake package into fedora
Date: Wed, 4 Nov 2009 02:38:28 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0911040236430.13299@localhost> (raw)
not sure if anyone involved with OE gets involved with this, but for
the sake of fedora folks, i'm trying to get an updated bitbake package
into fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=529067
obviously not critical, just convenient if it happens.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
next reply other threads:[~2009-11-04 7:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 7:38 Robert P. J. Day [this message]
2009-11-04 8:19 ` trying to get newest bitbake package into fedora Marcin Juszkiewicz
2009-11-04 8:24 ` Robert P. J. Day
2009-11-04 9:42 ` Richard Purdie
2009-11-04 10:03 ` Robert P. J. Day
2009-11-04 10:06 ` Robert P. J. Day
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.LFD.2.00.0911040236430.13299@localhost \
--to=rpjday@crashcourse.ca \
--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