From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH 3/3] isar-bootstrap: Eliminate no-gpg-check option usage
Date: Mon, 3 Dec 2018 13:52:04 +0100 [thread overview]
Message-ID: <4620e346-e7e8-273d-b128-dc93ce442cad@siemens.com> (raw)
In-Reply-To: <742259e5-876e-1c33-d6f2-af6448d98c58@ilbers.de>
On 03.12.18 12:49, Maxim Yu. Osipov wrote:
> On 11/7/18 7:09 PM, Maxim Yu. Osipov wrote:
>> Marking repo as trusted eliminates this option usage.
>
> Reverted in the 'next'.
>
Even a revert is a patch which requires reasoning. Please do so in the future.
Thanks,
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2018-12-03 12:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 16:09 [PATCH 0/3] bitbake upstream update and eliminate " Maxim Yu. Osipov
2018-11-07 16:09 ` [PATCH 1/3] Update bitbake from the upstream Maxim Yu. Osipov
2018-11-07 17:58 ` Henning Schild
2018-11-08 9:08 ` Maxim Yu. Osipov
2018-11-07 16:09 ` [PATCH 2/3] meta: Set LAYERSERIES_* variables Maxim Yu. Osipov
2018-11-07 16:20 ` Jan Kiszka
2018-11-07 16:39 ` Maxim Yu. Osipov
2018-11-07 16:41 ` Jan Kiszka
2018-11-07 17:24 ` Maxim Yu. Osipov
2018-11-07 17:26 ` Jan Kiszka
2018-11-07 16:09 ` [PATCH 3/3] isar-bootstrap: Eliminate no-gpg-check option usage Maxim Yu. Osipov
2018-11-07 17:38 ` Henning Schild
2018-11-08 7:57 ` Maxim Yu. Osipov
2018-11-12 9:30 ` Maxim Yu. Osipov
2018-11-27 9:43 ` Henning Schild
2018-11-27 10:15 ` Maxim Yu. Osipov
2018-12-03 11:49 ` Maxim Yu. Osipov
2018-12-03 12:52 ` Jan Kiszka [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=4620e346-e7e8-273d-b128-dc93ce442cad@siemens.com \
--to=jan.kiszka@siemens.com \
--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