From: Martin Jansa <martin.jansa@gmail.com>
To: Michael Halstead <mhalstead@linuxfoundation.org>
Cc: yocto@yoctoproject.org,
Paul Eggleton <paul.eggleton@linux.intel.com>,
bitbake-devel@lists.openembedded.org,
Openembedded-devel@lists.openembedded.org,
Openembedded-core@lists.openembedded.org
Subject: Re: [yocto] Patchwork users: Help test new version
Date: Thu, 23 Jun 2016 12:21:38 +0200 [thread overview]
Message-ID: <20160623102138.GA2567@jama> (raw)
In-Reply-To: <13986bd3-af12-4768-0a4c-78447c33c8b6@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 900 bytes --]
On Mon, Jun 20, 2016 at 10:47:16AM -0700, Michael Halstead wrote:
> Hello,
>
> OpenEmbedded is nearly ready to upgrade to a new version of Patchwork.
> The new version offers several new features that will allow OpenEmbedded
> to improve developer workflow and automated checks on incoming patches.
>
> If you are a Patchwork user please visit
> https://patchwork-next.openembedded.org/ and take a look. If you find
> anything amiss please e-mail me directly and include patchwork in the
> subject line.
>
> Thank you for your help upgrading this important system!
I was using it to update meta-oe/master-next in last few days and it
seems to work the same as old patchwork for me.
But quite often I've noticed very slow response, is it running on
slower HW while testing or is the new version just a lot slower?
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Martin Jansa <martin.jansa@gmail.com>
To: Michael Halstead <mhalstead@linuxfoundation.org>
Cc: yocto@yoctoproject.org,
Paul Eggleton <paul.eggleton@linux.intel.com>,
bitbake-devel@lists.openembedded.org,
Openembedded-devel@lists.openembedded.org,
Openembedded-core@lists.openembedded.org
Subject: Re: Patchwork users: Help test new version
Date: Thu, 23 Jun 2016 12:21:38 +0200 [thread overview]
Message-ID: <20160623102138.GA2567@jama> (raw)
In-Reply-To: <13986bd3-af12-4768-0a4c-78447c33c8b6@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 900 bytes --]
On Mon, Jun 20, 2016 at 10:47:16AM -0700, Michael Halstead wrote:
> Hello,
>
> OpenEmbedded is nearly ready to upgrade to a new version of Patchwork.
> The new version offers several new features that will allow OpenEmbedded
> to improve developer workflow and automated checks on incoming patches.
>
> If you are a Patchwork user please visit
> https://patchwork-next.openembedded.org/ and take a look. If you find
> anything amiss please e-mail me directly and include patchwork in the
> subject line.
>
> Thank you for your help upgrading this important system!
I was using it to update meta-oe/master-next in last few days and it
seems to work the same as old patchwork for me.
But quite often I've noticed very slow response, is it running on
slower HW while testing or is the new version just a lot slower?
--
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:[~2016-06-23 10:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 17:47 Patchwork users: Help test new version Michael Halstead
2016-06-20 17:47 ` Michael Halstead
2016-06-20 17:47 ` Michael Halstead
2016-06-20 17:47 ` Michael Halstead
2016-06-20 17:49 ` akuster
2016-06-20 21:53 ` [oe] " Burton, Ross
2016-06-20 21:53 ` Burton, Ross
2016-06-20 21:53 ` Burton, Ross
2016-06-23 10:21 ` Martin Jansa [this message]
2016-06-23 10:21 ` Martin Jansa
[not found] ` <0802a526-88ae-fd76-f024-77cb42509f8c@linux.intel.com>
2016-06-23 18:37 ` [OE-core] " Michael Halstead
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=20160623102138.GA2567@jama \
--to=martin.jansa@gmail.com \
--cc=Openembedded-core@lists.openembedded.org \
--cc=Openembedded-devel@lists.openembedded.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=mhalstead@linuxfoundation.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.