All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] htop: Update 1.0.2 -> 1.0.3
Date: Fri, 25 Apr 2014 21:22:48 +0100	[thread overview]
Message-ID: <535AC418.6070607@communistcode.co.uk> (raw)
In-Reply-To: <CAMKF1soef650vnpY3ca8JAXTAiP4KqWk-ksMP=Afncdg5KsDwA@mail.gmail.com>



On 25/04/2014 19:56, Khem Raj wrote:
> On Fri, Apr 25, 2014 at 11:26 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
>> "[oe] [meta-oe][PATCH 1/4] htop: upgrade to 1.0.3 and apply brokensep"
>
> inheriting autotools-brokensep is a workaround until we have fixed the
>   package proper intention should be to not use autotools-brokensep and
> fix the packages and use autotools-brokensep as last resort.
>

I agree, my fixes were just quick ones today which got me building. I 
would take Khems patch over mine as it seems to actually address the 
problem.

Cheers,


      reply	other threads:[~2014-04-25 20:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25 18:24 [meta-oe][PATCH] htop: Update 1.0.2 -> 1.0.3 Khem Raj
2014-04-25 18:26 ` Martin Jansa
2014-04-25 18:56   ` Khem Raj
2014-04-25 20:22     ` Jack Mitchell [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=535AC418.6070607@communistcode.co.uk \
    --to=ml@communistcode.co.uk \
    --cc=openembedded-devel@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.