Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: RFC: add BPN/BP to minimize boilerplate code for *-native (and similar) variants
Date: Thu, 16 Oct 2008 15:48:19 +0200	[thread overview]
Message-ID: <gd7gn3$esa$1@ger.gmane.org> (raw)
In-Reply-To: <48F743EF.90401@gmx.net>

On 16-10-2008 15:38, Robert Schuster wrote:
> Hi,
> please have a look at this bugzilla entry and the proposed patch:
>
> http://bugs.openembedded.net/show_bug.cgi?id=4735

Looks like it would save me from some repetetive monkey work :)


>
> Regards
> Robert
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel





  reply	other threads:[~2008-10-16 13:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-16 13:38 RFC: add BPN/BP to minimize boilerplate code for *-native (and similar) variants Robert Schuster
2008-10-16 13:48 ` Koen Kooi [this message]
2008-10-17 13:10   ` Robert Schuster

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='gd7gn3$esa$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox