From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: Ulf Magnusson <ulfalizer@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] scripts: add new script 'native'
Date: Mon, 3 Oct 2016 13:31:08 +0300 [thread overview]
Message-ID: <20161003103108.GA5762@linux.intel.com> (raw)
In-Reply-To: <CAFkk2KR5AB_gjq5XKFBJjOaaRHJ3DzJdCqS5H1Kq=m35xZ3jTQ@mail.gmail.com>
On Sun, Oct 02, 2016 at 04:30:58PM +0200, Ulf Magnusson wrote:
> On Sun, Oct 2, 2016 at 4:15 PM, Jérémy Rosen <jeremy.rosen@smile.fr> wrote:
> > "native" might be a bit too generic...
> >
> > could I suggest oe_native-run or bitbake-native ?
> >
> > something that says it's yocto-galaxy specific and can be autocompleted with
> > a reasonable prefix...
> >
> >
> > Jérémy Rosen
>
> I think overly namespacing things that aren't likely to clash in
> practice gets annoying. I would've gone for "run-native" (more
> descriptive and English-like, less generic), but how about something
> simple and easy to type like "oe-native" or "oe-run-native" if a
> prefix is added? That's consistent with the naming scheme used for
> many other scripts in scripts/ too.
>
I'm ok to rename it. I agree that 'native' may look too generic, but
I don't know about any existing tool with this name.
Anyway, let me know which name I should rename it to. Feel free to send a
patch too. I personally like 'oe-native' more than other proposals.
--
Regards,
Ed
prev parent reply other threads:[~2016-10-03 10:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 9:55 [PATCH] scripts: add new script Ed Bartosh
2016-09-28 15:00 ` Christopher Larson
2016-09-30 15:02 ` [PATCH v2] scripts: add new script 'native' Ed Bartosh
2016-10-02 14:15 ` Jérémy Rosen
2016-10-02 14:30 ` Ulf Magnusson
2016-10-02 14:44 ` Ulf Magnusson
2016-10-02 19:37 ` Paul Eggleton
2016-10-04 16:22 ` Randy MacLeod
2016-10-06 3:02 ` Paul Eggleton
2016-10-06 3:20 ` Ulf Magnusson
2016-10-06 3:29 ` Paul Eggleton
2016-10-03 10:31 ` Ed Bartosh [this message]
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=20161003103108.GA5762@linux.intel.com \
--to=ed.bartosh@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ulfalizer@gmail.com \
/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