From: Uladzimir Bely <ubely@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] dpkg: Do not warn about GIT_PROXY_COMMAND exports
Date: Fri, 22 Sep 2023 07:26:13 +0300 [thread overview]
Message-ID: <aba3b13f0b73126301f18af104d0a59c1d527be8.camel@ilbers.de> (raw)
In-Reply-To: <f818a8eb-f0ae-4b61-9f8f-12223770842d@siemens.com>
On Sat, 2023-09-16 at 15:49 +0530, Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> Latest bitbake now forwards this, causing our export check to raise a
> false alarm.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
>
> Visible when using kas-container, thus also with the recent kas
> patches.
>
> meta/classes/dpkg.bbclass | 1 +
> 1 file changed, 1 insertion(+)
Applied to next, thanks.
prev parent reply other threads:[~2023-09-22 4:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 10:19 Jan Kiszka
2023-09-22 4:26 ` Uladzimir Bely [this message]
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=aba3b13f0b73126301f18af104d0a59c1d527be8.camel@ilbers.de \
--to=ubely@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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