All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio.salvador@ossystems.com.br>
To: Costin Constantin <costin.c.constantin@intel.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 000/502] Include binaries in test cases and update runexported.py
Date: Fri, 18 Dec 2015 10:12:41 -0200	[thread overview]
Message-ID: <CAP9ODKowf_dvxoPjqV87GX7st=4VgpViq4eimcBE+oUOAm+Uqg@mail.gmail.com> (raw)
In-Reply-To: <cover.1450434192.git.costin.c.constantin@intel.com>

On Fri, Dec 18, 2015 at 10:22 AM, Costin Constantin
<costin.c.constantin@intel.com> wrote:
> The set of patches addresses Yocto binararies inclusion related features and
> updates to the runexported.py test launcher script for machines where poky
> environment is not available.
> As a result runtime test cases can be written to include native and target
> specific binaries, both packed as .rpm files or pre-unpacked for the situation
> where the remote target has no package manager. runexported.py includes new
> functionality.
>
> For all the above, enhancements are described in:
> [YOCTO #7850], [YOCTO #8478], [YOCTO #8479], [YOCTO #8481], [YOCTO #8530]
> [YOCTO #8534], [YOCTO #8535], [YOCTO #8536]
>
>
> The following changes since commit 1b25a70991589ed1f123015c16ee4806c46e3199:

This seems wrong; please check the way you called the pull request
script as it seems to have included other changes.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750


      reply	other threads:[~2015-12-18 12:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-18 12:22 [PATCH 000/502] Include binaries in test cases and update runexported.py Costin Constantin
2015-12-18 12:12 ` Otavio Salvador [this message]

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='CAP9ODKowf_dvxoPjqV87GX7st=4VgpViq4eimcBE+oUOAm+Uqg@mail.gmail.com' \
    --to=otavio.salvador@ossystems.com.br \
    --cc=costin.c.constantin@intel.com \
    --cc=openembedded-core@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.