From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] changelog encoding
Date: Sat, 9 Oct 2004 14:53:16 +0100 [thread overview]
Message-ID: <20041009145316.1c788f31@snowdrop.home> (raw)
In-Reply-To: <Pine.LNX.4.58.0410081958130.21079@ybec.rq.iarg>
[-- Attachment #1: Type: text/plain, Size: 880 bytes --]
On Fri, 8 Oct 2004 20:05:16 -0500 (EST) Ed Grimm
<paranoid@gentoo.evolution.tgape.org> wrote:
| On Fri, 8 Oct 2004, Ciaran McCreesh wrote:
| > As I recall, 127 is flaky. Come to think of it, so is 0-31ish as
| > well. So maybe I should've said
| > [a-zA-Z0-9\-_,.<>?/\\;:'@#~\]{}\+="$%^&* ] or something...
| > Basically, anything even the slightest bit flaky, plus newlines, is
| > prone to explode.
|
| I hope you like long lines.
Well, remember that there's no standard way of doing newlines. Or that
there're at least three standards, depending upon how you look at it.
Eh, not that this is really relevant anyway. All that matters is that
ASCII is insufficient and that UTF-8 is most likely the best
alternative.
--
Ciaran McCreesh : Gentoo Developer (Sparc, MIPS, Vim, Fluxbox)
Mail : ciaranm at gentoo.org
Web : http://dev.gentoo.org/~ciaranm
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-09 13:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 15:29 Fw: [gentoo-portage-dev] changelog encoding Marius Mauch
2004-10-08 16:26 ` Luke-Jr
2004-10-08 16:40 ` Ciaran McCreesh
2004-10-09 1:05 ` Ed Grimm
2004-10-09 13:53 ` Ciaran McCreesh [this message]
2004-10-09 15:24 ` Brian
2004-10-09 17:10 ` Ciaran McCreesh
2004-10-09 17:38 ` Marius Mauch
-- strict thread matches above, loose matches on Subject: below --
2004-10-08 4:19 Brian
2004-10-08 12:31 ` Marius Mauch
2004-10-08 17:34 ` George Shapovalov
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=20041009145316.1c788f31@snowdrop.home \
--to=ciaranm@gentoo.org \
--cc=gentoo-portage-dev@lists.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