From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Patchwork almost clean
Date: Thu, 24 Jul 2014 05:29:13 -1000 [thread overview]
Message-ID: <53D12649.3020000@balister.org> (raw)
In-Reply-To: <20140724141403.GL2492@jama>
[-- Attachment #1: Type: text/plain, Size: 1476 bytes --]
Thanks Martin!
Philip
On 07/24/2014 04:14 AM, Martin Jansa wrote:
> There are still 30 changes in master-next bundle:
> http://patchwork.openembedded.org/bundle/jama/master-next/?archive=both
>
> Some are new, some are old WIPs I haven't finished, some are still also
> in master-next branch on way to master (after review comments are
> addressed)
>
> 63b95b7 ipsec-tools: several fixes
> efba173 snort: do not hardcode the libdir
> 135879a openvpn: not use the hardcoded libdir
> 2c137e4 syslog-ng: Improved initscript VERBOSE handling.
> caa7815 xterm: disable-rpath-hack to avoid QA issue
> e8203c9 meta-python: rename recipes-python to recipes-devtools
> d5ee15e wireshark: Add missing pkgconfig dependency
> f444b38 libxml-filter-buffertext-perl: add recipe
> 17da3f6 libxml-sax-writer-perl: add recipe
> d9c9bd1 wireshark: fix build for arm
> 67c9ab3 wireshark: Add recipe 1.12.0-rc2
> 1b0361a packagegroups: Remove deprecated "task" backward compatibility
> 36e9829 monkey: new v1.5.1 release.
> dc95fd1 usb-modeswitch: Upgrade to latest version
> dd6e944 tcpslice: add recipe under tcpdump
> ee0b865 opencv: Bump SRCREV to 2.4.9 release tag, PV is now 2.4.9+git.
> 8e8a40f opencv: Disable 'gtk' backend if X11 is not available
> 19f1992 php 5.4.14: use pkg-config for libxml2 detection
> ddddaa7 mplayer2: Inherit python3native
>
> Please check if you've submitted one of these commits and please update its state.
>
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 550 bytes --]
prev parent reply other threads:[~2014-07-24 15:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 14:14 Patchwork almost clean Martin Jansa
2014-07-24 15:29 ` Philip Balister [this message]
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=53D12649.3020000@balister.org \
--to=philip@balister.org \
--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