From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: meta-oe patch queue
Date: Sun, 19 Jan 2014 10:06:26 +0100 [thread overview]
Message-ID: <20140119090626.GA3742@jama> (raw)
[-- Attachment #1: Type: text/plain, Size: 638 bytes --]
Apologies for delay, there is blocking jenkins job running for 10days
already (which should take 40minutes tops).
It should finish very soon (well I'm thinking that since Monday).
For better visibility and consistency with oe-core, I've started pushing
my patch queue from patchwork "in-test" bundle (I'll rename it to
"master-next" when it's emptier) to
meta-openembedded/master-next
instead of
meta-openembedded-contrib/jansa/in-test
Please test patches in master-next and send reviews on ML, but be aware
that it's rebased often on top of master.
BTW: there is also meta-qt5/master-next now (with 5.2)
Cheers,
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next reply other threads:[~2014-01-19 9:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-19 9:06 Martin Jansa [this message]
2014-01-22 11:12 ` meta-oe patch queue Otavio Salvador
-- strict thread matches above, loose matches on Subject: below --
2014-04-20 14:25 Martin Jansa
2014-04-21 17:06 ` Stephen Arnold
2014-04-21 17:22 ` Stephen Arnold
2014-04-21 17:25 ` Martin Jansa
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=20140119090626.GA3742@jama \
--to=martin.jansa@gmail.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 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.