From: Clark Rawlins <clark.rawlins@escient.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gzip cpio
Date: Thu, 21 Jun 2007 06:40:03 -0400 [thread overview]
Message-ID: <1182422403.7911.2.camel@venture.bit63.org> (raw)
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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: target-cpio.patch
Type: text/x-patch
Size: 1059 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20070621/86e2606c/attachment.bin
next reply other threads:[~2007-06-21 10:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 10:40 Clark Rawlins [this message]
2007-06-21 11:21 ` [Buildroot] [PATCH] gzip cpio Bernhard Fischer
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=1182422403.7911.2.camel@venture.bit63.org \
--to=clark.rawlins@escient.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