public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Bernhard Reutner-Fischer" <rep.dot.nop@gmail.com>,
	"Björn Stenberg" <bjst@enea.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/8] Revert "Add ptest for glib."
Date: Tue, 05 Feb 2013 16:44:03 +0000	[thread overview]
Message-ID: <1360082643.28450.3.camel@ted> (raw)
In-Reply-To: <3666e39a359b03ba1e054813f4353ddeed11d506.1360079373.git.rep.dot.nop@gmail.com>

On Tue, 2013-02-05 at 16:55 +0100, Bernhard Reutner-Fischer wrote:
> This reverts commit dec6f912d68f52748f645b6af411f189cf464f85.
> 
> This breaks core-image-sato-sdk for TCLIBC="uclibc".
> 
> Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
> ---
>  .../glib-2.0/glib-2.0/Makefile-ptest.patch         |   61 --------------------
>  meta/recipes-core/glib-2.0/glib-2.0/run-ptest      |    3 -
>  meta/recipes-core/glib-2.0/glib-2.0_2.34.3.bb      |   22 -------
>  3 files changed, 86 deletions(-)
>  delete mode 100644 meta/recipes-core/glib-2.0/glib-2.0/Makefile-ptest.patch
>  delete mode 100644 meta/recipes-core/glib-2.0/glib-2.0/run-ptest

How about we fix ptest for glib? The revert isn't really the direction
we want to take the project. At least discussing this with Björn (cc'd)
and/or filing a bug would be a good idea before we move to reverting it.

Cheers,

Richard




  reply	other threads:[~2013-02-05 17:00 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-05 15:55 [PATCH 0/8] misc tweaks Bernhard Reutner-Fischer
2013-02-05 15:55 ` [PATCH 1/8] base.bbclass: Commentary typo fix Bernhard Reutner-Fischer
2013-02-05 15:55 ` [PATCH 2/8] uclibc: add c6x arch Bernhard Reutner-Fischer
2013-02-05 15:55 ` [PATCH 3/8] uclibc: turn on kernel module support Bernhard Reutner-Fischer
2013-02-05 15:55 ` [PATCH 4/8] Revert "Add ptest for glib." Bernhard Reutner-Fischer
2013-02-05 16:44   ` Richard Purdie [this message]
2013-02-05 16:44   ` Burton, Ross
2013-02-05 16:47     ` Bernhard Reutner-Fischer
2013-02-05 16:59       ` Burton, Ross
2013-02-05 17:17         ` Bernhard Reutner-Fischer
2013-02-08  8:21           ` Björn Stenberg
2013-02-05 16:46   ` Saul Wold
2013-02-05 17:13     ` Bernhard Reutner-Fischer
2013-02-05 18:39       ` Saul Wold
2013-02-05 19:16         ` Bernhard Reutner-Fischer
2013-02-05 19:36           ` Bernhard Reutner-Fischer
2013-02-05 19:59             ` Saul Wold
2013-02-06  0:01               ` Khem Raj
2013-02-06  9:02         ` Björn Stenberg
2013-02-05 15:55 ` [PATCH 5/8] busybox: add ifup's ifstate dir to package Bernhard Reutner-Fischer
2013-02-12  5:46   ` Saul Wold
2013-02-12  9:14     ` Bernhard Reutner-Fischer
2013-02-05 15:55 ` [PATCH 6/8] busybox: update-modules script needs id(1) Bernhard Reutner-Fischer
2013-02-05 16:38   ` Richard Purdie
2013-02-05 16:46     ` Bernhard Reutner-Fischer
2013-02-05 15:55 ` [PATCH 7/8] base.bbclass: remove redundant setting of MAKE Bernhard Reutner-Fischer
2013-02-05 15:55 ` [PATCH 8/8] create-pull-request: Error message on missing -u Bernhard Reutner-Fischer

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=1360082643.28450.3.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bjst@enea.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rep.dot.nop@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox