From: Robert Millan <rmh@aybabtu.com>
To: grub-devel@gnu.org
Cc: Ward Vandewege <ward@gnu.org>, coreboot@coreboot.org
Subject: Re: [PATCH] split tar & cpio
Date: Sun, 8 Feb 2009 00:42:31 +0100 [thread overview]
Message-ID: <20090207234231.GA11319@thorin> (raw)
In-Reply-To: <20081108161715.GA7474@thorin>
On Sat, Nov 08, 2008 at 05:17:15PM +0100, Robert Millan wrote:
>
> Hi,
>
> I thought it would be a good idea to split tar & cpio into separate modules
> to save some space and make things easier to figure out for the users. I
> managed to do this without duplicating code, with a bit of pre-processor
> magic.
>
> The saved size is not much, though (~400 bytes). But users looking for tar
> will find it more easily. How do you feel about this? Is it worth it?
Committed.
coreboot users: if you're using tar to generate GRUB's memdisk image, with
latest svn you need to include tar.mod instead of cpio.mod.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
prev parent reply other threads:[~2009-02-07 23:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-08 16:17 [PATCH] split tar & cpio Robert Millan
2009-02-07 23:42 ` Robert Millan [this message]
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=20090207234231.GA11319@thorin \
--to=rmh@aybabtu.com \
--cc=coreboot@coreboot.org \
--cc=grub-devel@gnu.org \
--cc=ward@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.