All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: Christopher Larson <clarson@kergoth.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] mkefidisk.sh: add deprecation warning to the output
Date: Tue, 8 Nov 2016 01:02:58 +0200	[thread overview]
Message-ID: <20161107230258.GB7754@linux.intel.com> (raw)
In-Reply-To: <CABcZANkm7CbH8pOHi5Wo3oN=usiCfX9kmOr6fPp9j9-M7E0AMg@mail.gmail.com>

On Thu, Nov 03, 2016 at 07:23:24PM -0700, Christopher Larson wrote:
> On Thu, Nov 3, 2016 at 2:42 PM, Khem Raj <raj.khem@gmail.com> wrote:
> 
> > > On Oct 31, 2016, at 3:46 AM, Ed Bartosh <ed.bartosh@linux.intel.com>
> > wrote:
> > >
> > > mkefidisk.sh will soon be deprecated in favor of .wic images.
> > >
> > > Added deprecation warning to the script to inform users that
> > > this script will soon be removed from the codebase.
> > >
> > > Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
> > > ---
> > > scripts/contrib/mkefidisk.sh | 5 +++++
> > > 1 file changed, 5 insertions(+)
> > >
> > > diff --git a/scripts/contrib/mkefidisk.sh b/scripts/contrib/mkefidisk.sh
> > > index d8db3c0..a175895 100755
> > > --- a/scripts/contrib/mkefidisk.sh
> > > +++ b/scripts/contrib/mkefidisk.sh
> > > @@ -20,6 +20,11 @@
> > >
> > > LANG=C
> > >
> > > +echo
> > > +echo "WARNING: This script is deprecated and will be removed soon."
> > > +echo "Please consider using wic EFI images instead."
> > > +echo
> > > +
> >
> > is .wic image dd’able directly ?
> >
> 
> Yes, that’s the point :) Though I prefer bmaptool w/ IMAGE_FSTYPES +=
> “wic.bmap” personally, don’t have to rely on the file keeping its
> sparseness when scp’ing it around and whatnot.

Recommending bmaptool as a preferred way of flashing is in the plans :)

--
Regards,
Ed


  reply	other threads:[~2016-11-07 23:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-31 10:46 [PATCH] mkefidisk.sh: add deprecation warning to the output Ed Bartosh
2016-11-03 21:42 ` Khem Raj
2016-11-04  2:23   ` Christopher Larson
2016-11-07 23:02     ` Ed Bartosh [this message]
2016-11-07 23:00   ` Ed Bartosh
2016-11-07 23:44     ` Khem Raj
2016-11-08 20:44       ` Randy Witt
     [not found]         ` <77d63518-4bd4-0688-438b-07778f754733@intel.com>
2016-11-09  8:05           ` Ed Bartosh

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=20161107230258.GB7754@linux.intel.com \
    --to=ed.bartosh@linux.intel.com \
    --cc=clarson@kergoth.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.