From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>,
Naveen Saini <naveen.kumar.saini@intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v4] grub: upgrade 2.04 -> 2.06~rc1
Date: Fri, 19 Mar 2021 17:33:05 +0000 [thread overview]
Message-ID: <4dae32cd7ff6573010af48a2d54eac0d6201cc94.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAMKF1sr1X99rgF2G1vdyrb-i3bfDPcj3NSxoXV-A8Mw7nxRbNw@mail.gmail.com>
On Fri, 2021-03-19 at 10:04 -0700, Khem Raj wrote:
> I think renaming recipe to drop PV from its name is not a good as this
> makes it harder for bbappends to be version specific or atleast cause
> an event to upgrade
>
Having "~" in a filename probably isn't too sensible either though?
Cheers,
Richard
next prev parent reply other threads:[~2021-03-19 17:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 7:14 [PATCH v4] grub: upgrade 2.04 -> 2.06~rc1 Naveen Saini
2021-03-19 17:04 ` [OE-core] " Khem Raj
2021-03-19 17:33 ` Richard Purdie [this message]
2021-03-23 15:41 ` Khem Raj
[not found] <166DAC6771B8A6FC.4881@lists.openembedded.org>
2021-03-30 1:59 ` Naveen Saini
2021-03-30 2:19 ` Khem Raj
2021-03-30 13:11 ` Zoltan Boszormenyi
2021-03-30 14:36 ` Steve Sakoman
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=4dae32cd7ff6573010af48a2d54eac0d6201cc94.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=naveen.kumar.saini@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@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