public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: Re: [PATCH] Drop redundant expand=True parameter from getVar
Date: Mon, 06 Mar 2023 09:03:26 +0300	[thread overview]
Message-ID: <2091735.9o76ZdvQCi@home> (raw)
In-Reply-To: <2c213737-daca-5546-4d2a-d358d1dffbec@siemens.com>

In the email from Tuesday, 28 February 2023 10:24:07 +03 user Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
> 
> It is long True by default, but people keep adding new cases of this
> redundancy. Fix at least the existing ones via
> 
> for f in $(git ls-tree --name-only -r HEAD meta*); do
>     sed -i "s/\(getVar([^,]*\), True)/\1)/g" $f;
> done
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> 
> Please double-check that I all conversions are correct and that I didn't 
> touch any file that is supposed to stay in sync with OE (I don't think 
> so).
> 
>  meta-isar/recipes-app/hello/hello.bb          |  2 +-
>  meta/classes/base.bbclass                     | 20 ++++++-------
>  meta/classes/buildchroot.bbclass              |  2 +-
>  meta/classes/dpkg-base.bbclass                | 20 ++++++-------
>  meta/classes/dpkg.bbclass                     |  4 +--
>  meta/classes/image-account-extension.bbclass  |  6 ++--
>  meta/classes/image-locales-extension.bbclass  |  4 +--
>  meta/classes/image-tools-extension.bbclass    |  2 +-
>  meta/classes/image.bbclass                    | 10 +++----
>  meta/classes/imagetypes_wic.bbclass           | 18 ++++++------
>  meta/classes/initramfs.bbclass                |  2 +-
>  meta/classes/isar-events.bbclass              |  2 +-
>  meta/classes/rootfs.bbclass                   |  4 +--
>  meta/classes/sbuild.bbclass                   |  2 +-
>  meta/classes/sdk.bbclass                      |  6 ++--
>  meta/classes/template.bbclass                 |  8 +++---
>  .../isar-bootstrap/isar-bootstrap.inc         | 28 +++++++++----------
>  meta/recipes-kernel/kselftest/kselftest.inc   |  6 ++--
>  meta/recipes-kernel/linux/linux-custom.inc    | 14 +++++-----
>  meta/recipes-kernel/linux/linux-distro.bb     | 10 +++----
>  20 files changed, 85 insertions(+), 85 deletions(-)
> 

Applied to next, thanks.




  reply	other threads:[~2023-03-06  6:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28  7:24 Jan Kiszka
2023-03-06  6:03 ` Uladzimir Bely [this message]
2024-05-24  6:52 srinuvasan.a
2024-05-24  7:27 ` MOESSBAUER, Felix
2024-05-24  8:38 ` Anton Mikanovich
2024-05-27  5:38   ` Srinuvasan Arjunan
2024-06-03  6:37 ` Uladzimir Bely

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=2091735.9o76ZdvQCi@home \
    --to=ubely@ilbers.de \
    --cc=isar-users@googlegroups.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