From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: roberto.foglietta@linuxteam.org
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH v7] image tools ext.: start_imager_session not break the rebuild, v7
Date: Tue, 10 Jan 2023 05:40:10 +0100 [thread overview]
Message-ID: <CAJGKYO6oVPnW6fBRokDkz+17W3=WykeMNiex=Cqx-wgGNZ+1=g@mail.gmail.com> (raw)
In-Reply-To: <20230110042438.1226639-1-roberto.foglietta@linuxteam.org>
On Tue, 10 Jan 2023 at 05:24, <roberto.foglietta@linuxteam.org> wrote:
>
> From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
>
> image tools extension, start_imager_session, bugfix and improvement
>
> The original Ilbers ISAR code was buggy but the 1st fix do not improve
> the performances nore solved completely the problem which has been
> definitely addressed in part.2 - then this p.3 aims to improve the
> performance brutally deleting the closing schroot session without relies
> on the slower and sometimes failing schroot -e python script.
>
> p.1: bugfix, initial
> p.2: bugfix completed, code rationalisation
> p.3: performance improvement bypassing schroot -e and Co.
> v.4: the squash of the three parts
> v.5: deep reworking
> v.6: bug fixing
> v.7: removed the code left behind but not used
>
> Signed-off-by: Roberto A. Foglietta <roberto.foglietta@gmail.com>
> ---
> meta/classes/image-tools-extension.bbclass | 39 ++++++++--------------
> meta/classes/isar-events.bbclass | 31 +++++++++++------
> meta/classes/sbuild.bbclass | 3 +-
> 3 files changed, 37 insertions(+), 36 deletions(-)
>
This patch has no impact on building time (1 sec or less) nor disk
usage or storage.
Best regards, R-
prev parent reply other threads:[~2023-01-10 4:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 4:24 roberto.foglietta
2023-01-10 4:40 ` Roberto A. Foglietta [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='CAJGKYO6oVPnW6fBRokDkz+17W3=WykeMNiex=Cqx-wgGNZ+1=g@mail.gmail.com' \
--to=roberto.foglietta@gmail.com \
--cc=isar-users@googlegroups.com \
--cc=roberto.foglietta@linuxteam.org \
/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