From: Joe MacDonald <Joe_MacDonald@mentor.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: meta-networking pending patches
Date: Thu, 16 Apr 2015 00:18:39 -0400 [thread overview]
Message-ID: <20150416041839.GA4366@mentor.com> (raw)
In-Reply-To: <20150413110235.GC2330@jama>
[-- Attachment #1: Type: text/plain, Size: 1981 bytes --]
Hi Martin,
[Re: meta-networking pending patches] On 15.04.13 (Mon 13:02) Martin Jansa wrote:
> On Tue, Mar 10, 2015 at 02:30:30PM +0100, Martin Jansa wrote:
> > Hi Joe,
> >
> > can you please check pending meta-networking patches?
> >
> > my master-next shows:
> > pick e7be331 openl2tp: add new recipe
> > pick 64461e1 ipvsadm: Add version 1.26 (initial recipe)
> > pick f5ba5af netkit-telnet: add new recipe
> > pick 1e6dd99 iscsi-initiator-utils: fix SELinux label for initiatorname.iscsi
> > pick 8a09ac6 vlan: install vconfig into /sbin same as Ubuntu and Fedora.
> > pick 6fdadbe stunnel: Update to version 5.10
> > pick e74b325 postfix: add link file /usr/lib/sendmail
> > pick 64de50c wireshark: update to 12.4
> > pick 4428a44 crda: move libnl, libgcrypt to DEPENDS
> > pick 5cd9417 esmtp: update sendmail link files
> >
> > and few more are in patchwork:
> > http://patchwork.openembedded.org/bundle/jama/meta-networking/?archive=both
>
> Another round pending in my master-next:
>
> pick 6a89b66 ipvsadm: Add version 1.26 (initial recipe)
> pick 5f63e35 wolfssl: change name from cyassl to wolfssl, update to version 3.4.0
> pick 446c0cf vpnc: don't rdepend on kernel-module-tun
> pick e44ecd9 vsftpd / init: add LSB init infos
> pick 5033f44 postfix: add LSB init infos
Merged and the patches are updated in patchworks. Most were simple, the
ipvsadm one had been outstanding for quite a while as I'd requested
changes in it. I merged the patch from master-next and made the
correction myself before pushing it, since I never did see a v4 and
there wasn't an obvious update in patchworks.
>
> I plan to create "fido" branch today, so all these will need to go
> through fido maintainers if you want to merge them in fido release as
> well.
I sent out patches tagged for-fido, since I missed the window to get
them merged prior to the branch by a few days.
-J.
>
> Regards,
>
--
-Joe MacDonald.
:wq
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 484 bytes --]
next prev parent reply other threads:[~2015-04-16 4:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 13:30 meta-networking pending patches Martin Jansa
2015-04-13 11:02 ` Martin Jansa
2015-04-16 4:18 ` Joe MacDonald [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-03-10 13:44 MacDonald, Joe
2015-03-10 22:27 ` Joe MacDonald
2015-03-11 12:39 ` Martin Jansa
2015-03-11 16:27 ` Joe MacDonald
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=20150416041839.GA4366@mentor.com \
--to=joe_macdonald@mentor.com \
--cc=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.