public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>,
	Claudius Heine <ch@denx.de>,
	claudius.heine.ext@siemens.com
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH v4 1/9] isar-bootstrap-host: disable DISTRO_APT_KEYS usage
Date: Fri, 26 Apr 2019 13:47:00 +0200	[thread overview]
Message-ID: <3049e852-9f55-390e-fc40-94d5774ef6e1@siemens.com> (raw)
In-Reply-To: <ff192a96-3853-449f-4c10-818e1c1a3905@ilbers.de>

On 26.04.19 13:22, Maxim Yu. Osipov wrote:
> On 4/26/19 12:45 PM, Claudius Heine wrote:
>> Quoting Claudius Heine (2019-04-26 12:39:27)
>>> Quoting Maxim Yu. Osipov (2019-04-26 10:41:16)
>>>> I need more arguments for introduction of this limitation.
>>>
>>> Again, that limitation is already present. I don't get why you are
>>> often so sure of yourself, especially about code you have not written
>>> or worked with intensively.
> 
> I suggest you to choose the correct words before writing such kind of sentences. 
> I'm not a boy and you are not my mentor.
> 
>> Ok sorry, I take that back. You have written and worked with this code.
>> I thought that was written mostly by Alex.
> 
> It doesn't matter if this my code or not.
> 
> I'm quite tired from this offensive style of communication - I consider such 
> style as misbehavior. I hope that was my last warning to you.
> 

In general, I would appreciate when everyone focuses more again on understanding 
the issues we still have in code base and tooling, rather then discussing about 
where they came from, who to blame and who should therefore fix them. And the 
result needs to be understandable for the core contributors - and ideally not 
only for them.

Of course, if there is evidence that a particular way of working is inefficient, 
a way of designing is causing problems too often, please make that transparent, 
with facts.

Thanks,
Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2019-04-26 11:47 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25 13:44 [PATCH v4 0/9] Cleanup rootfs creation claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 1/9] isar-bootstrap-host: disable DISTRO_APT_KEYS usage claudius.heine.ext
2019-04-25 18:20   ` Maxim Yu. Osipov
2019-04-26  7:36     ` Claudius Heine
2019-04-26  8:41       ` Maxim Yu. Osipov
2019-04-26 10:39         ` Claudius Heine
2019-04-26 10:45           ` Claudius Heine
2019-04-26 11:22             ` Maxim Yu. Osipov
2019-04-26 11:47               ` Jan Kiszka [this message]
2019-04-30  9:34         ` Andreas Reichel
2019-04-30 13:30           ` Maxim Yu. Osipov
2019-04-30 15:22             ` Andreas Reichel
2019-04-30 15:30               ` Jan Kiszka
2019-04-30 15:46               ` Maxim Yu. Osipov
2019-05-02 12:14                 ` Andreas Reichel
2019-04-26 11:31       ` Jan Kiszka
2019-04-26 11:50         ` Jan Kiszka
2019-05-14  9:22           ` Fwd: " Maxim Yu. Osipov
2019-05-14 11:32           ` Claudius Heine
2019-05-14 11:35             ` Claudius Heine
2019-04-25 13:44 ` [PATCH v4 2/9] isar-bootstrap-helper: move 'HOST_ARCH' and 'HOST_DISTRO' to base.bbclass claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 3/9] move 'HOST_DISTRO_APT_SOURCES' from bootstrap-helper to isar-bootstrap claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 4/9] buildchroot.bbclass: only cross build if HOST_ARCH != DISTRO_ARCH claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 5/9] isar-bootstrap/buildchroot/sdkchroot: refactor PF and WORKDIR claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 6/9] bitbake.conf: remove unneeded and differently used variables claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 7/9] image.bbclass: make IMAGE_ROOTFS overwritable claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 8/9] bitbake.conf: set default QEMU_ARCH variables claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 9/9] buildchroot/configscript: make creation of builder uid/gid idempotent claudius.heine.ext

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=3049e852-9f55-390e-fc40-94d5774ef6e1@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=ch@denx.de \
    --cc=claudius.heine.ext@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