From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Before you ping some older patches
Date: Wed, 22 Feb 2017 22:32:54 +0100 [thread overview]
Message-ID: <20170222213254.GH3283@jama> (raw)
[-- Attachment #1: Type: text/plain, Size: 964 bytes --]
1) Make sure they aren't already in master (or master-next), currently
there is only one change in master-next:
eb7979113 netcat-openbsd: fix implicit dependency on pkg-config
2) Make sure there weren't some negative feedback comments on our change
3) Make sure the change made it to patchwork, currently there is only
one "open" change:
https://patchwork.openembedded.org/patch/137499/
Be aware that the changes are usually daily marked as archived, when
they are sorted to corresponding bundles and included in master-next
branch for testing, as described here:
http://www.openembedded.org/wiki/Patchwork#Multiple_layers_sharing_the_same_oe_project_on_patchwork
I'm writing this, because currently many changes are missing on patchwork,
because of some unknown issue with it, see:
http://lists.openembedded.org/pipermail/openembedded-devel/2017-February/111467.html
once this issue is resolved, please re-send missing changes.
Regards,
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
next reply other threads:[~2017-02-22 21:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 21:32 Martin Jansa [this message]
2017-02-22 23:06 ` Before you ping some older patches Michael Halstead
2017-02-22 23:48 ` Martin Jansa
2017-02-23 0:08 ` Michael Halstead
2017-02-23 0:20 ` Derek Straka
2017-02-23 1:53 ` Martin Jansa
2017-02-23 1:58 ` Michael Halstead
2017-02-23 2:31 ` Michael Halstead
-- strict thread matches above, loose matches on Subject: below --
2017-02-22 22:26 MacDonald, Joe
2017-02-22 22:51 ` Martin Jansa
2017-02-22 23:09 MacDonald, Joe
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=20170222213254.GH3283@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox