public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Claudius Heine <claudius.heine.ext@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>, isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: Re: [PATCH v2 0/8] Cleanup rootfs creation
Date: Wed, 24 Apr 2019 08:53:33 +0200	[thread overview]
Message-ID: <24e19870-6d4c-3258-e568-b8e77d7158e2@siemens.com> (raw)
In-Reply-To: <c96b9cca-e46a-90ea-0b6c-4186449c3709@ilbers.de>

Hi Maxim,

On 22/04/2019 15.48, Maxim Yu. Osipov wrote:
> The same problem with SDK creation discovered in v1 series persists also 
> in v2 series.
> 
> Just recognized that "quick" CI build fails too. See for details:
> http://isar-build.org:8080/job/isar_mosipov_develop/91/console
> 
> Please run CI scripts before submitting patches to the mailing list - 

I did:

http://isar-build.org:8080/job/isar_claudius_ilbers-ci/46/consoleText

That build just fails because of the qemu boot where loading of modules 
fails for some reason, but you said that could be ignored.

> this will save maintainer's time.

Well if you are short on time, then I would suggest looking into better 
tooling.

There are solutions that could automate most of the job you do as a 
maintainer, meaning loading patchset from mailinglist, processing it in 
CI and reporting results back to the mailinglist.

Probably something like this:
https://that.guru/blog/patchwork-and-ci-in-a-tree/

As I suggested months ago that patchwork can help safe time and avoid 
leaving any patches behind. If you don't look into solutions like that 
or write your own scripting, then I don't see much reason for you to 
complain.

By doing that, you might even have enough time to start doing code 
reviews and taking part in design discussions etc. where it is much 
better invested that just pushing the "Run CI build" button and waiting 
for that to finish.

To be fair I might do you injustice and you are performing thorough 
review of every ones patches and every ones code is just that excellent 
that only grammar and spelling mistakes in commit messages are left to 
critic, but then it might just be a matter of improving communication.

Claudius

> 
> Maxim.
> 
> On 4/17/19 1:11 PM, claudius.heine.ext@siemens.com wrote:
>> From: Claudius Heine <ch@denx.de>
>>
>> Hi,
>>
>> this is the fixed up version.
>>
>> regards,
>> Claudius
>>
>> changes from v1:
>>   - fixed typo in commit message
>>
>> Claudius Heine (8):
>>    isar-boostrap-helper: move 'HOST_ARCH' and 'HOST_DISTRO' to
>>      base.bbclass
>>    move 'HOST_DISTRO_APT_SOURCES' from bootstrap-helper to isar-bootstrap
>>    buildchroot.bbclass: only cross build if HOST_ARCH != DISTRO_ARCH
>>    isar-bootstrap/buildchroot/sdkchroot: refactor PF and WORKDIR
>>    bitbake.conf: remove unneeded and differently used variables
>>    image.bbclass: make IMAGE_ROOTFS overwritable
>>    bitbake.conf: set default QEMU_ARCH variables
>>    buildchroot/configscript: make creation of builder uid/gid idempotent
>>
>>   meta/classes/base.bbclass                          |  9 +++++++++
>>   meta/classes/buildchroot.bbclass                   |  2 +-
>>   meta/classes/image-sdk-extension.bbclass           |  2 +-
>>   meta/classes/image.bbclass                         |  2 +-
>>   meta/classes/isar-bootstrap-helper.bbclass         | 14 --------------
>>   meta/conf/bitbake.conf                             | 13 ++++++++-----
>>   .../isar-bootstrap/isar-bootstrap-host.bb          | 11 +++--------
>>   .../isar-bootstrap/isar-bootstrap-target.bb        |  6 +-----
>>   .../recipes-core/isar-bootstrap/isar-bootstrap.inc |  1 +
>>   .../buildchroot/buildchroot-host.bb                |  1 +
>>   meta/recipes-devtools/buildchroot/buildchroot.inc  |  3 +--
>>   .../buildchroot/files/configscript.sh              |  4 ++--
>>   meta/recipes-devtools/sdkchroot/sdkchroot.bb       |  3 +--
>>   13 files changed, 30 insertions(+), 41 deletions(-)
>>
> 
> 

-- 
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

  reply	other threads:[~2019-04-24  6:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-17 11:11 claudius.heine.ext
2019-04-17 11:11 ` [PATCH v2 1/8] isar-boostrap-helper: move 'HOST_ARCH' and 'HOST_DISTRO' to base.bbclass claudius.heine.ext
2019-04-17 11:11 ` [PATCH v2 2/8] move 'HOST_DISTRO_APT_SOURCES' from bootstrap-helper to isar-bootstrap claudius.heine.ext
2019-04-17 11:11 ` [PATCH v2 3/8] buildchroot.bbclass: only cross build if HOST_ARCH != DISTRO_ARCH claudius.heine.ext
2019-04-17 11:11 ` [PATCH v2 4/8] isar-bootstrap/buildchroot/sdkchroot: refactor PF and WORKDIR claudius.heine.ext
2019-04-17 11:11 ` [PATCH v2 5/8] bitbake.conf: remove unneeded and differently used variables claudius.heine.ext
2019-04-17 11:11 ` [PATCH v2 6/8] image.bbclass: make IMAGE_ROOTFS overwritable claudius.heine.ext
2019-04-17 11:11 ` [PATCH v2 7/8] bitbake.conf: set default QEMU_ARCH variables claudius.heine.ext
2019-04-17 11:11 ` [PATCH v2 8/8] buildchroot/configscript: make creation of builder uid/gid idempotent claudius.heine.ext
2019-04-22 13:48 ` [PATCH v2 0/8] Cleanup rootfs creation Maxim Yu. Osipov
2019-04-24  6:53   ` Claudius Heine [this message]
2019-04-24  8:00     ` Maxim Yu. Osipov
2019-04-24  8:18       ` 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=24e19870-6d4c-3258-e568-b8e77d7158e2@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