From: "Livius" <egyszeregy@freemail.hu>
To: openembedded-core@lists.openembedded.org
Subject: Re: [master][PATCH] image_types: add 7-Zip support in conversion types and commands
Date: Fri, 26 Aug 2022 07:22:47 -0700 [thread overview]
Message-ID: <24076.1661523767736620054@lists.openembedded.org> (raw)
In-Reply-To: <20220826120220.18071b38@booty>
[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]
I can not use 'git send-email' because my workstation is not configured to be able to send any mail. You can use my patch, the content is available under '--' what is need to for it, or I can copy and paste it and re-send to this thread. But in 2022, I really recommend to you to improve your contributing processes more. It could be much better in a modern pull-request ticket in GitHub, GitLab or Bitbucket portal then this historical mode. That kind of process is too legacy, and it can not help in developing speed and to get more-more users/contributors who want to help in daily developing.
My goal was replacing wic.zip conversion, because it is extremely slowly for an image which is several GB sizes. Problem is that normal zip can operate only in single-thread mode, but 7-zip can do it in multi-thread mode in much faster if I use BZip2 method for a zip archive. I liked to provide .zip extension because BZip2 support it, and it is fine for multiplatform usage, in 100% you can unzip it in Windows, Linux and OSX too. So, my new wic.7zip can operate in 100% CPU load in each 8 cores of my CPU, therefore this is the best for making a .zip file for wic image. But if someone wants to use any other mode, they can do with variables overriding.
[-- Attachment #2: Type: text/html, Size: 1297 bytes --]
next prev parent reply other threads:[~2022-08-26 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 19:59 [master][PATCH] image_types: add 7-Zip support in conversion types and commands Livius
2022-08-26 10:02 ` [OE-core] " Luca Ceresoli
2022-08-26 14:22 ` Livius [this message]
2022-11-06 13:34 ` Livius
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=24076.1661523767736620054@lists.openembedded.org \
--to=egyszeregy@freemail.hu \
--cc=openembedded-core@lists.openembedded.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