Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Discussion of the angstrom distribution development
	<angstrom-distro-devel@linuxtogo.org>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [Angstrom-devel] current build errors, OE dev branch, beagleboard-linuxtag2010-demo-image
Date: Wed, 2 Jun 2010 03:54:57 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.1006020354160.3418@lynx> (raw)
In-Reply-To: <20100602065840.GI5446@jama>

On Wed, 2 Jun 2010, Martin Jansa wrote:

> Robert: If I remember right, you were asked few times to use tinderbox
> instead sending many e-mails with pastebins, why didn't you follow this
> advise yet?

  you're right, i'd forgotten about tinderbox.  my apologies, i'll use
that from now on.

  and i've just done a pull on the OE dev branch and i'm trying
another build of the linuxtag target to see what's left to resolve.

rday

-- 

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================



  reply	other threads:[~2010-06-02  7:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.DEB.2.00.1006011641480.17094@lynx>
     [not found] ` <4C057DFC.6010409@mlbassoc.com>
     [not found]   ` <alpine.DEB.2.00.1006011753350.30834@lynx>
     [not found]     ` <20100601220233.GG5446@jama>
     [not found]       ` <4C058898.60202@mlbassoc.com>
2010-06-02  6:58         ` [Angstrom-devel] current build errors, OE dev branch, beagleboard-linuxtag2010-demo-image Martin Jansa
2010-06-02  7:54           ` Robert P. J. Day [this message]
2010-06-02 12:08           ` Gary Thomas

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=alpine.DEB.2.00.1006020354160.3418@lynx \
    --to=rpjday@crashcourse.ca \
    --cc=angstrom-distro-devel@linuxtogo.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox