All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe MacDonald <Joe_MacDonald@mentor.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: meta-networking pending patches
Date: Wed, 11 Mar 2015 12:27:50 -0400	[thread overview]
Message-ID: <20150311162750.GA4894@mentor.com> (raw)
In-Reply-To: <20150311123902.GA6713@jama>

[-- Attachment #1: Type: text/plain, Size: 2546 bytes --]

[Re: [oe] meta-networking pending patches] On 15.03.11 (Wed 13:39) Martin Jansa wrote:

> 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

Sure.  I'm working on reviewing the other outstanding ones now.

> > > 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.

Okay, good to know.  I've completely switched to using pwclient for my
workflow, but I'll try to keep on top of the outliers as well.  Unless
there's a pwclient-friendly way to work with bundles.  I haven't found
anything while poking around except some out-of-tree patches from ~6y
ago.  If you notice something lingering in the bundle, please go ahead
and ping me on it.

-- 
-Joe MacDonald.
:wq

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 501 bytes --]

  reply	other threads:[~2015-03-11 16:27 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
2015-03-11 16:27     ` Joe MacDonald [this message]
  -- 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=20150311162750.GA4894@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.