From: Claudius Heine <claudius.heine.ext@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>
Cc: isar-users@googlegroups.com, Claudius Heine <ch@denx.de>
Subject: Re: [PATCH v4 1/3] isar-bootstrap|configscript: implement one shot config option
Date: Tue, 29 May 2018 12:56:10 +0200 [thread overview]
Message-ID: <781ae027-0ca9-1aac-7099-651134a92714@siemens.com> (raw)
In-Reply-To: <da066a1b-fdc0-98c9-3a3b-ff51fd32dd7b@siemens.com>
On 2018-05-29 10:20, [ext] Claudius Heine wrote:
>>> # SPDX-License-Identifier: MIT
>>> +IMAGE_CFG_PACKAGE ??= ""
>>
>> Are you going to rename this variable to IMAGE_CFG_PACKAGES
>> and add a comment it in a separate patch?
>
> Oh, sorry. Forgot about that. I will prepare v5.
I have thought on this and I think that 'IMAGE_CFG_PACKAGES' is a bad
variable name, since it implies to be the variable to put all
configuration packages into.
How about 'IMAGE_ONESHOT_PACKAGES', 'IMAGE_VOLATILE_PACKAGES' or
'IMAGE_TEMPORARY_PACKAGES'?
Claudius
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de
next prev parent reply other threads:[~2018-05-29 10:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 10:56 [PATCH v4 0/3] One-shot configuration packages claudius.heine.ext
2018-05-28 10:56 ` [PATCH v4 1/3] isar-bootstrap|configscript: implement one shot config option claudius.heine.ext
2018-05-29 7:58 ` Maxim Yu. Osipov
2018-05-29 8:20 ` Claudius Heine
2018-05-29 10:56 ` Claudius Heine [this message]
2018-05-29 11:18 ` Maxim Yu. Osipov
2018-05-29 11:38 ` Claudius Heine
2018-05-28 10:56 ` [PATCH v4 2/3] meta/isar-cfg-localepurge: added locale purge recipe claudius.heine.ext
2018-05-28 10:56 ` [PATCH v4 3/3] meta-isar/isar-image-base: switch use isar-cfg-localepurge claudius.heine.ext
2018-05-29 8:00 ` [PATCH v4 0/3] One-shot configuration packages Baurzhan Ismagulov
2018-05-29 9:29 ` Claudius Heine
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=781ae027-0ca9-1aac-7099-651134a92714@siemens.com \
--to=claudius.heine.ext@siemens.com \
--cc=ch@denx.de \
--cc=isar-users@googlegroups.com \
--cc=mosipov@ilbers.de \
/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