From: richard.purdie@linuxfoundation.org
To: Joshua Watt <JPEW.hacker@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] multiconfig: Adapt to bitbake switch 'multiconfig' -> 'mc'
Date: Fri, 07 Jun 2019 17:23:52 +0100 [thread overview]
Message-ID: <c0cb96272d5dd5dddfe61dfbee2f428156b124d9.camel@linuxfoundation.org> (raw)
In-Reply-To: <ff680a45-8b31-6167-d5b5-e1a242fc006d@gmail.com>
On Fri, 2019-06-07 at 10:51 -0500, Joshua Watt wrote:
> Is there a reason for this change other than aesthetics?
I have had a lot of complaints and in real world use I can understand
why...
> FWIW, we maintain some recipes across several versions of poky, so
> this rename is going to cause me some headaches
The mcdepends code is tollerant of either naming. We could teach cooker
to translate any commandline references so both worked there. Would
that be good enough to work for you?
Cheers,
Richard
next prev parent reply other threads:[~2019-06-07 16:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 15:48 [PATCH] multiconfig: Adapt to bitbake switch 'multiconfig' -> 'mc' Richard Purdie
2019-06-07 15:51 ` Joshua Watt
2019-06-07 16:23 ` richard.purdie [this message]
2019-06-07 16:30 ` Joshua Watt
2019-06-10 17:53 ` Alejandro Hernandez
2019-06-11 9:02 ` richard.purdie
2019-06-07 20:08 ` akuster808
2019-06-07 20:27 ` Joshua Watt
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=c0cb96272d5dd5dddfe61dfbee2f428156b124d9.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=JPEW.hacker@gmail.com \
--cc=openembedded-core@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