From: Thomas Kunze <thommycheck@gmx.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: mtn disapprove
Date: Sun, 13 Jan 2008 14:09:16 +0100 [thread overview]
Message-ID: <1200229756.6056.4.camel@HD> (raw)
In-Reply-To: <fma5d5$5k5$1@ger.gmane.org>
On Sat, 2008-01-12 at 11:39 +0100, Rolf Leggewie wrote:
> Thomas,
>
> thank you for your suggestion. Please correct me if I misunderstand you.
>
> Thomas Kunze schrieb:
> > I would also move the PACKAGE_ARCH stuff.
>
> You suggest to move the PACKAGE_ARCH stuff out of the inc file and into
> the individual config files? For what benefit? They are common for all
> machines except for the collie, so I believe .inc is the best place for
> that.
The same is true for "include tune-xscale.inc". So one could use
include_collie (if this is possible). But the other way is IMO cleaner.
Have only things in zaurus-2.6.inc that are common to all zaurus. OTOH
it may make sense to separate collie from the other zaurus because
collie doesn't have much in common with them.
>
> Regards
>
> Rolf
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2008-01-13 13:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 7:36 mtn disapprove Koen Kooi
2008-01-11 8:30 ` Rolf Leggewie
2008-01-11 8:38 ` Koen Kooi
2008-01-11 16:53 ` Rolf Leggewie
2008-01-11 18:48 ` Rolf Leggewie
2008-01-11 19:20 ` Koen Kooi
2008-01-11 19:32 ` Rolf Leggewie
2008-01-11 23:22 ` Thomas Kunze
2008-01-12 10:39 ` Rolf Leggewie
2008-01-13 13:09 ` Thomas Kunze [this message]
2008-01-13 15:06 ` Rolf Leggewie
2008-01-13 16:30 ` Koen Kooi
2008-01-14 11:21 ` Florian Boor
2008-01-14 11:44 ` Rolf Leggewie
2008-01-11 19:36 ` Rolf Leggewie
2008-01-11 11:06 ` ohviey1
-- strict thread matches above, loose matches on Subject: below --
2008-01-11 20:57 QMan
2008-01-12 10:42 ` Rolf Leggewie
2008-01-12 11:41 ` Richard Purdie
2008-01-13 20:26 QMan
2008-01-28 13:51 ` Rolf Leggewie
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=1200229756.6056.4.camel@HD \
--to=thommycheck@gmx.de \
--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.