From: maht <maht-qemu@mail.maht0x0r.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qcow3 - arbitrary metadata
Date: Tue, 29 Jul 2008 07:40:55 +0100 [thread overview]
Message-ID: <op.ue1jihdvi9u4k6@step1> (raw)
In-Reply-To: <a38baa500807282022l2c113a77y23dad0e3afb217ea@mail.gmail.com>
For what it's worth from an outsider, imho in-band singnalling (which is
what arbitrary meta-data is) is bone-headed.
It's the same reason extended attributes are stupid.
You are going to poison your file format because you think command line
arguments are cumbersome. You're then going to need a set of extra tools
to modify said metadata, you wont be able to use the standard set of tools
sed/grep/awk/ed to change them. You're going to have to add code to parse
them and over-ride them; for what ? Because you think a script is untidy.
Plus, for all your talk about the subject you could have coded it up by
now!
Plus la change.
Matt
next prev parent reply other threads:[~2008-07-29 7:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 19:56 [Qemu-devel] [PATCH] qcow3 - arbitrary metadata Nathaniel McCallum
2008-07-28 20:08 ` Anthony Liguori
2008-07-28 20:24 ` Nathaniel McCallum
2008-07-28 20:36 ` Paul Brook
2008-07-28 20:52 ` Anthony Liguori
2008-07-28 20:50 ` Anthony Liguori
2008-07-28 21:12 ` Nathaniel McCallum
2008-07-28 21:17 ` Anthony Liguori
2008-07-28 21:19 ` Nathaniel McCallum
2008-07-28 21:39 ` Anthony Liguori
2008-07-29 1:49 ` Jamie Lokier
2008-07-29 2:11 ` Jorge Lucángeli Obes
2008-07-29 2:48 ` Nathaniel McCallum
2008-07-29 3:05 ` Jorge Lucángeli Obes
2008-07-29 3:13 ` Anthony Liguori
2008-07-29 6:44 ` Jamie Lokier
2008-07-29 13:38 ` Anthony Liguori
2008-07-29 16:05 ` Jamie Lokier
2008-07-29 8:48 ` Daniel P. Berrange
2008-07-28 23:04 ` Laurent Vivier
2008-07-29 1:25 ` Nathaniel McCallum
2008-07-29 3:06 ` Anthony Liguori
2008-07-29 3:22 ` Nathaniel McCallum
2008-07-29 6:40 ` maht [this message]
2008-07-29 6:44 ` maht
2008-07-29 7:48 ` Laurent Vivier
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=op.ue1jihdvi9u4k6@step1 \
--to=maht-qemu@mail.maht0x0r.net \
--cc=qemu-devel@nongnu.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.