From: Joe MacDonald <joe@deserted.net>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-networking][PATCH] openflow: Add latest from git
Date: Wed, 4 Sep 2013 17:04:30 -0400 [thread overview]
Message-ID: <20130904210427.GQ3761@deserted.net> (raw)
In-Reply-To: <CADkTA4NOCjzDz=SXqAx+AxDTDztSas5EG+i74LUmpaF0OkZ5SQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]
[Re: [oe] [meta-networking][PATCH] openflow: Add latest from git] On 13.09.04 (Wed 08:22) Bruce Ashfield wrote:
> On Tue, Sep 3, 2013 at 11:27 PM, Joe MacDonald <joe@deserted.net> wrote:
> > On Tue, Sep 3, 2013 at 6:39 PM, Bruce Ashfield <bruce.ashfield@gmail.com> wrote:
> >>
...
> >> - We run some tests against meta-virt and give you the thumbs up when it
> >> is safe to merge, and the meta-virt copy can be deleted. I definitely don't
> >> want two of these running around.
> >
> > I don't mind delaying a merge a bit while waiting for more feedback on
> > testing, provided we're talking about a reasonable timeframe.
> > Otherwise, if the submitted OpenFlow is working well enough in
> > meta-net, I'm inclined to merge it and take patches from you guys if
> > you find issues down the road. That'll be how it will work anyway in
> > three month's time, for example, when meta-virt has dropped their
> > copy.
> >
> > How long do you think you'll need on this?
>
> I can test the new SRCREV and recipe by the end of the day, assuming
> that you have the slightly edited version by the time I'm done, there
> shouldn't be any incurred delay.
Great, thanks. Let me know how it goes.
--
-Joe MacDonald.
:wq
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-09-04 21:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 8:20 [meta-networking][PATCH] openflow: Add latest from git Laszlo Papp
2013-09-03 1:56 ` Bruce Ashfield
2013-09-03 3:55 ` Laszlo Papp
2013-09-03 13:04 ` Bruce Ashfield
2013-09-03 13:13 ` Laszlo Papp
2013-09-03 13:38 ` Bruce Ashfield
2013-09-03 13:47 ` Laszlo Papp
2013-09-03 21:18 ` Joe MacDonald
2013-09-04 21:02 ` Joe MacDonald
2013-09-03 21:08 ` Joe MacDonald
2013-09-03 22:39 ` Bruce Ashfield
2013-09-04 3:27 ` Joe MacDonald
2013-09-04 12:22 ` Bruce Ashfield
2013-09-04 21:04 ` Joe MacDonald [this message]
2013-09-05 4:29 ` Bruce Ashfield
2013-09-04 13:13 ` Philip Balister
2013-09-04 13:31 ` Laszlo Papp
2013-09-04 20:26 ` Joe MacDonald
2013-09-04 21:14 ` Joe MacDonald
2013-09-05 4:39 ` Bruce Ashfield
2013-09-05 9:01 ` Burton, Ross
2013-09-05 9:13 ` Laszlo Papp
2013-09-05 13:04 ` Joe MacDonald
2013-09-05 13:07 ` Laszlo Papp
2013-09-05 13:01 ` Joe MacDonald
2013-09-05 5:05 ` Laszlo Papp
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=20130904210427.GQ3761@deserted.net \
--to=joe@deserted.net \
--cc=bruce.ashfield@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.