From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gzip cpio
Date: Thu, 21 Jun 2007 13:21:52 +0200 [thread overview]
Message-ID: <20070621112152.GA21096@aon.at> (raw)
In-Reply-To: <1182422403.7911.2.camel@venture.bit63.org>
On Thu, Jun 21, 2007 at 06:40:03AM -0400, Clark Rawlins wrote:
>This patch is useful to me. It permits gzipping the cpio archive after
>creation. This is my first attempt so if there are better, or more
>correct ways to accomplish this I am interested in improving my changes.
Problem is that somebody will show up sooner or later who wants to use
another compressor (we've seen this with ext2 rootfs).
Let me suggest you look at target/ext2/ext2root.mk
and do the same COMPRESSOR fiddling (with cpio and any other target
format).
thanks,
next prev parent reply other threads:[~2007-06-21 11:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 10:40 [Buildroot] [PATCH] gzip cpio Clark Rawlins
2007-06-21 11:21 ` Bernhard Fischer [this message]
2007-08-01 17:18 ` Chris Malarky
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=20070621112152.GA21096@aon.at \
--to=rep.dot.nop@gmail.com \
--cc=buildroot@busybox.net \
/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