From: Trevor Woerner <twoerner@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: yocto@yoctoproject.org,
openembedded-architecture@lists.openembedded.org,
openembedded-core@lists.openembedded.org
Subject: Re: Patchwork and incoming patch testing
Date: Wed, 18 Jan 2017 22:54:30 -0500 [thread overview]
Message-ID: <20170119035430.GA24183@linux-uys3> (raw)
In-Reply-To: <2683342.SVnRAGIE1W@peggleto-mobl.ger.corp.intel.com>
On Wed 2017-01-18 @ 07:05:58 AM, Paul Eggleton wrote:
> This should give us a bit more visibility into
> where patches are at in the process, although we are still working on a few
> places where patch series status needs to be updated (e.g. when a patch goes
> into testing).
Is the testing process for OE patches formalized?
I'm not referring to the Yocto Project's release testing.
WARNING: multiple messages have this Message-ID (diff)
From: Trevor Woerner <twoerner@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: yocto@yoctoproject.org,
openembedded-architecture@lists.openembedded.org,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] Patchwork and incoming patch testing
Date: Wed, 18 Jan 2017 22:54:30 -0500 [thread overview]
Message-ID: <20170119035430.GA24183@linux-uys3> (raw)
In-Reply-To: <2683342.SVnRAGIE1W@peggleto-mobl.ger.corp.intel.com>
On Wed 2017-01-18 @ 07:05:58 AM, Paul Eggleton wrote:
> This should give us a bit more visibility into
> where patches are at in the process, although we are still working on a few
> places where patch series status needs to be updated (e.g. when a patch goes
> into testing).
Is the testing process for OE patches formalized?
I'm not referring to the Yocto Project's release testing.
next prev parent reply other threads:[~2017-01-19 3:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 18:05 Patchwork and incoming patch testing Paul Eggleton
2017-01-17 19:56 ` [Openembedded-architecture] " Denys Dmytriyenko
2017-01-18 8:40 ` Jussi Kukkonen
2017-01-18 14:52 ` [yocto] " Leonardo Sandoval
2017-01-18 14:52 ` Leonardo Sandoval
2017-01-18 15:06 ` [yocto] " Jose Lamego
2017-01-18 22:40 ` Jose Lamego
2017-01-18 22:47 ` [OE-core] " Jose Lamego
2017-01-19 3:54 ` Trevor Woerner [this message]
2017-01-19 3:54 ` [OE-core] " Trevor Woerner
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=20170119035430.GA24183@linux-uys3 \
--to=twoerner@gmail.com \
--cc=openembedded-architecture@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=yocto@yoctoproject.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.