All of lore.kernel.org
 help / color / mirror / Atom feed
From: richard.purdie@linuxfoundation.org
To: Alejandro Hernandez
	<alejandro.enedino.hernandez-samaniego@xilinx.com>,
	 Joshua Watt <jpewhacker@gmail.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] multiconfig: Adapt to bitbake switch 'multiconfig' -> 'mc'
Date: Tue, 11 Jun 2019 10:02:02 +0100	[thread overview]
Message-ID: <72dbb4c10b7e7d4eedbcc8a60a93e80b168dbafd.camel@linuxfoundation.org> (raw)
In-Reply-To: <b950d0d5-6ef3-37fc-29de-15bd0fed7c7a@xilinx.com>

On Mon, 2019-06-10 at 10:53 -0700, Alejandro Hernandez wrote:
> On 6/7/2019 9:30 AM, Joshua Watt wrote:
> > On 6/7/19 11:23 AM, richard.purdie@linuxfoundation.org wrote:
> > > 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?
> > 
> > Ya, that would be sufficient. I'll work up a patch for that.
> 
> I believe that I originally named it 'multiconfig' to try to make it 
> more explicit for users,

I remember the discussions and I was fairly strongly in favour of
"multiconfig" as well...

> but if people think its more intuitive to use 'mc' I'm not against
> it, using either also works for me.

On balance its proving annoying to people and the feedback I'm getting
is people strongly prefer "mc:", even if it makes me think midnight
commander! :)

Cheers,

Richard



  reply	other threads:[~2019-06-11  9:02 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
2019-06-07 16:30     ` Joshua Watt
2019-06-10 17:53       ` Alejandro Hernandez
2019-06-11  9:02         ` richard.purdie [this message]
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=72dbb4c10b7e7d4eedbcc8a60a93e80b168dbafd.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alejandro.enedino.hernandez-samaniego@xilinx.com \
    --cc=jpewhacker@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 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.