Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] coreutils: Move stdbuf into an own package coreutils-stdbuf
Date: Sun, 27 Oct 2019 17:04:10 +0200	[thread overview]
Message-ID: <20191027150410.GB31803@localhost> (raw)
In-Reply-To: <3fa389507f352aab06a4e084039e0bcf68bde9b1.camel@linuxfoundation.org>

On Tue, Oct 22, 2019 at 01:50:05PM +0100, Richard Purdie wrote:
> 
> This seems to break core-utils-native:
> 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/39/builds/1157
>...

Thanks, v3 sent.

> Cheers,
> 
> Richard

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



      reply	other threads:[~2019-10-27 15:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-04 14:20 [PATCH v2] coreutils: Move stdbuf into an own package coreutils-stdbuf Adrian Bunk
2019-10-22 12:50 ` Richard Purdie
2019-10-27 15:04   ` Adrian Bunk [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=20191027150410.GB31803@localhost \
    --to=bunk@stusta.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox