From: Martin Jansa <martin.jansa@gmail.com>
To: Joe MacDonald <Joe_MacDonald@mentor.com>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: meta-networking pending patches
Date: Wed, 11 Mar 2015 13:39:02 +0100 [thread overview]
Message-ID: <20150311123902.GA6713@jama> (raw)
In-Reply-To: <20150310222718.GB4083@mentor.com>
[-- Attachment #1: Type: text/plain, Size: 3552 bytes --]
On Tue, Mar 10, 2015 at 06:27:18PM -0400, Joe MacDonald wrote:
> [Re: [oe] meta-networking pending patches] On 15.03.10 (Tue 13:44) MacDonald, Joe wrote:
>
> > Sure thing. I'll have a look today and update the status appropriately.
> >
> > -J.
> >
> > On 10 Mar 2015 06:30, Martin Jansa <martin.jansa@gmail.com> wrote:
> > Hi Joe,
> >
> > can you please check pending meta-networking patches?
> >
> > my master-next shows:
> > pick e7be331 openl2tp: add new recipe
>
> This has already been merged (ab75a8c8d0a57411af1452f9f8f41ccf29bb0cc7)
> and I don't see it in my patchworks list now. The filter I'm using is
> this:
>
> http://patchwork.openembedded.org/project/oe/list/?state=1&q=meta-networking&archive=both
OK, master-next version was adding it to recipes-daemons instead of
recipes-protocols, that's why it wasn't resolved when rebasing
master-next. Will drop it now from master-next.
Please use meta-networking bundle as filter as well:
http://patchwork.openembedded.org/bundle/jama/meta-networking/?archive=both
http://www.openembedded.org/wiki/Patchwork#Multiple_layers_sharing_the_same_oe_project_on_patchwork
> > pick 64461e1 ipvsadm: Add version 1.26 (initial recipe)
>
> I placed this one in 'rework' state on January 26th after requesting a
> clarification on the bash requirement and suggesting at least one of the
> patches be tweaked.
>
> http://article.gmane.org/gmane.comp.handhelds.openembedded/67476
>
> I haven't seen a follow-up on it, but it looks like master-next has the
> v3 that I commented on.
OK
> > pick f5ba5af netkit-telnet: add new recipe
>
> It looks like this was merged (56e58865851a3160c49d9929011a0eccc9b0c8e2)
> and I'm not seeing it in my filter.
again master-next version had it in different directory
recipes-daemons and merged version is recipes-netkit, will drop it from
master-next.
> > pick 1e6dd99 iscsi-initiator-utils: fix SELinux label for initiatorname.iscsi
>
> This was dropped in favour of the version going to meta-selinux. I
> updated patchworks to indicate it was being reworked a while back.
OK, dropping from master-next.
> > pick 8a09ac6 vlan: install vconfig into /sbin same as Ubuntu and Fedora.
>
> I've merged this today.
thanks
> > pick 6fdadbe stunnel: Update to version 5.10
>
> This got missed in my regular filter for obvious reasons. I've merged
> it as well.
thanks
> > 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
>
> These were already in my queue but I've dumped them in favour of the
> cherry-picks.
thanks
> > and few more are in patchwork:
> > http://patchwork.openembedded.org/bundle/jama/meta-networking/?archive=both
>
> The others in this list also look like they were missed because they
> didn't contain the meta-networking tag in the subject line. Are you
> manually creating that bundle or do you just have better filtering
> technology than I do for catching these oddball ones?
I'm maintaining all bundles manually
First I add to bundles based on e-mail prefix, but then when I'm reading
the commits for cherry-picking them to master-next I sometimes notice
that the patch is touching some layer without saying so in subject
prefix and I add these oddball onces to separate bundle just before
cherry-pick.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2015-03-11 12:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 13:44 meta-networking pending patches MacDonald, Joe
2015-03-10 22:27 ` Joe MacDonald
2015-03-11 12:39 ` Martin Jansa [this message]
2015-03-11 16:27 ` Joe MacDonald
-- strict thread matches above, loose matches on Subject: below --
2015-03-10 13:30 Martin Jansa
2015-04-13 11:02 ` Martin Jansa
2015-04-16 4:18 ` 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=20150311123902.GA6713@jama \
--to=martin.jansa@gmail.com \
--cc=Joe_MacDonald@mentor.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.