From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>,
"Schmidt, Adriaan" <adriaan.schmidt@siemens.com>
Subject: Re: [PATCH 0/3] Sparse tar generation
Date: Thu, 21 Apr 2022 18:05:49 +0200 [thread overview]
Message-ID: <e715453c-a783-2050-d70f-f4a83d2b8292@siemens.com> (raw)
In-Reply-To: <cover.1646498090.git.jan.kiszka@siemens.com>
On 05.03.22 17:34, Jan Kiszka wrote:
> Just some small optimization: Consistently use tar -S when generating
> archives to avoid expanding sparse files.
>
> Jan
>
> Jan Kiszka (3):
> sstate: Generate image packages using sparse
> targz-img: Handle sparse files efficiently
> vm-img: Handle sparse files efficiently
>
> meta/classes/rootfs.bbclass | 2 +-
> meta/classes/targz-img.bbclass | 2 +-
> meta/classes/vm-img.bbclass | 6 +++---
> meta/recipes-core/isar-bootstrap/isar-bootstrap.inc | 2 +-
> 4 files changed, 6 insertions(+), 6 deletions(-)
>
Ping for patch 1 and 2 (3 is dropped due to breaking compatibility),
specifically towards Adriaan.
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
next prev parent reply other threads:[~2022-04-21 16:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-05 16:34 Jan Kiszka
2022-03-05 16:34 ` [PATCH 1/3] sstate: Generate image packages using sparse Jan Kiszka
2022-05-24 19:03 ` Jan Kiszka
2022-03-05 16:34 ` [PATCH 2/3] targz-img: Handle sparse files efficiently Jan Kiszka
2022-03-07 9:02 ` Henning Schild
2022-03-07 9:43 ` Jan Kiszka
2022-03-05 16:34 ` [PATCH 3/3] vm-img: " Jan Kiszka
2022-03-07 9:04 ` Henning Schild
2022-03-07 9:46 ` Jan Kiszka
2022-03-07 14:09 ` Henning Schild
2022-03-07 14:41 ` Jan Kiszka
2022-03-07 14:53 ` Henning Schild
2022-04-21 16:05 ` Jan Kiszka [this message]
2022-04-25 6:04 ` [PATCH 0/3] Sparse tar generation Anton Mikanovich
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=e715453c-a783-2050-d70f-f4a83d2b8292@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=adriaan.schmidt@siemens.com \
--cc=isar-users@googlegroups.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