Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: ChenQi <Qi.Chen@windriver.com>,
	Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] devtool: warn user about multiple layer having the same base name
Date: Fri, 28 Jun 2019 10:09:22 +0000	[thread overview]
Message-ID: <c2dc0472ed9646f680f658e4297eb4df@xbox06.axis.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 537 bytes --]

I had not realized the layer name in the devtool finish command supports abbreviations/patterns (whichever it is). My expectation from running `devtool finish foo meta` would be to update the foo recipe in the meta layer,  not that it should go looking for every layer called meta-something.

How useful is that support compared to be able to specify the exact layer name? Normally in this situation, I would typically expect to use an extra option,  e.g., --abbrev or --regexp, to enable support for using loose matching.

//Peter

[-- Attachment #2: Type: text/html, Size: 737 bytes --]

             reply	other threads:[~2019-06-28 10:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-28 10:09 Peter Kjellerstedt [this message]
2019-06-30 20:24 ` [PATCH 1/1] devtool: warn user about multiple layer having the same base name Paul Eggleton
  -- strict thread matches above, loose matches on Subject: below --
2019-06-27  3:14 [PATCH 0/1] " Chen Qi
2019-06-27  3:14 ` [PATCH 1/1] " Chen Qi
2019-06-27 23:25   ` Paul Eggleton
2019-06-28  1:20     ` ChenQi

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=c2dc0472ed9646f680f658e4297eb4df@xbox06.axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=Qi.Chen@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.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