From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 2/2] Renamed prefix_native, bindir_native, etc using camelCaps
Date: Thu, 18 Mar 2010 17:29:02 +0000 [thread overview]
Message-ID: <1268933342.8697.43.camel@rex> (raw)
In-Reply-To: <201003180437.10542.holger+oe@freyther.de>
On Thu, 2010-03-18 at 04:37 +0100, Holger Hans Peter Freyther wrote:
> On Thursday 18 March 2010 02:31:11 Douglas Royds wrote:
> > - Avoids clashing with the machine override when MACHINE=native
> > - bindir_cross similarly renamed for consistency
>
> Thank you for that much work. I think we established the usage of '-' instead
> of '_' to avoid clashes with the override detection though.
I just noticed this problem. It makes me very very nervous to introduce
yet another variable naming convention, particularly one we don't use
anywhere else :/.
Might it be simpler to rename the native machine? Using "native" in the
override namespace is asking for trouble :(.
Cheers,
Richard
next prev parent reply other threads:[~2010-03-18 17:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 1:31 [PATCH 2/2] Renamed prefix_native, bindir_native, etc using camelCaps Douglas Royds
2010-03-18 3:37 ` Holger Hans Peter Freyther
2010-03-18 17:29 ` Richard Purdie [this message]
2010-03-18 17:49 ` Koen Kooi
2010-03-18 19:42 ` Richard Purdie
2010-03-18 19:55 ` Khem Raj
2010-03-18 20:58 ` Douglas Royds
2010-03-18 21:19 ` Richard Purdie
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=1268933342.8697.43.camel@rex \
--to=rpurdie@rpsys.net \
--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