All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel@openembedded.org
Subject: Re: pushing mamona things upstream
Date: Thu, 23 Oct 2008 19:16:31 -0400	[thread overview]
Message-ID: <20081023231631.GB21151@denix.org> (raw)
In-Reply-To: <bdb0025f0810222159ka9b7ab7q4088bd6a241e477a@mail.gmail.com>

On Thu, Oct 23, 2008 at 01:59:11AM -0300, Rodrigo Vivi wrote:
> My plan is to send directly all patches that change mamona packages,
> tasks and configuration.

Thanks for doing it.

> This shouldn't break anyone's build. (Get prepared for an avalanche of 
> commits :) )

At least in theory. But in reality it got broken:

ERROR: Could not include required file ../gcc/gcc3-build.inc while parsing /OE/openembedded/packages/mamona/gcc-noemu_4.1.2.bb

You forgot the gcc/gcc3-build.inc and BitBake chokes on it while parsing the 
tree.

-- 
Denys



  parent reply	other threads:[~2008-10-23 23:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-23  4:59 pushing mamona things upstream Rodrigo Vivi
2008-10-23  5:52 ` Marcin Juszkiewicz
2008-10-23 23:16 ` Denys Dmytriyenko [this message]
2008-10-24  3:40   ` Ricardo Salveti
2008-10-27 13:07     ` Michael 'Mickey' Lauer

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=20081023231631.GB21151@denix.org \
    --to=denis@denix.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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.