From: Adriaan Schmidt <adriaan.schmidt@siemens.com>
To: <isar-users@googlegroups.com>
Cc: Adriaan Schmidt <adriaan.schmidt@siemens.com>
Subject: [PATCH v2 0/2] Sparse tar generation
Date: Mon, 11 Jul 2022 09:11:53 +0200 [thread overview]
Message-ID: <20220711071155.776897-1-adriaan.schmidt@siemens.com> (raw)
Sorry it took me so long to review!
Just some small optimization: Consistently use tar -S when generating
archives to avoid expanding sparse files.
Changes since v1:
- dropped p3
- rebased p2 to fit with new imagetypes
Jan Kiszka (2):
sstate: Generate image packages using sparse
targz-img: Handle sparse files efficiently
meta/classes/imagetypes.bbclass | 2 +-
meta/classes/rootfs.bbclass | 2 +-
meta/recipes-core/isar-bootstrap/isar-bootstrap.inc | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
--
2.30.2
next reply other threads:[~2022-07-11 7:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 7:11 Adriaan Schmidt [this message]
2022-07-11 7:11 ` [PATCH v2 1/2] sstate: Generate image packages using sparse Adriaan Schmidt
2022-07-11 7:11 ` [PATCH v2 2/2] targz-img: Handle sparse files efficiently Adriaan Schmidt
2022-07-19 18:56 ` [PATCH v2 0/2] 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=20220711071155.776897-1-adriaan.schmidt@siemens.com \
--to=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