From: Sven Vermeulen <swift@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] GLEP 34: Per-Category metadata.xml Files
Date: Tue, 15 Mar 2005 09:59:31 +0100 [thread overview]
Message-ID: <4236A3F3.5090301@gentoo.org> (raw)
In-Reply-To: <20050313153816.56c6f684@snowdrop>
Ciaran McCreesh wrote:
[...]
> It is proposed that the existing ``metadata.xml`` format [1]_ be used.
> Even though XML sucks, there is already a framework in place for these
> files. The filename will be ``blah-misc/metadata.xml``. The character set
> used shall be UTF-8 for consistency with GLEP 31 [2]_.
Perhaps you might want to remove any subjective opinions from the GLEP.
Specifically, "XML sucks", since it doesn't suck. People just abuse it
too much.
Wkr,
Sven Vermeulen
--
^__^ And Larry saw that it was Good.
(oo) Sven Vermeulen
(__) http://www.gentoo.org Documentation & PR
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2005-03-15 8:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-13 15:38 [gentoo-dev] GLEP 34: Per-Category metadata.xml Files Ciaran McCreesh
2005-03-15 8:59 ` Sven Vermeulen [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=4236A3F3.5090301@gentoo.org \
--to=swift@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.gentoo.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