From: Andrew Haley <aph@redhat.com>
To: <classpath@gnu.org>, "Mauve Discuss" <mauve-discuss@sources.redhat.com>
Subject: RE: java.util.Date mess
Date: Tue, 12 Oct 2004 09:41:00 -0000 [thread overview]
Message-ID: <16747.42661.267373.605540@cuddles.cambridge.redhat.com> (raw)
In-Reply-To: <D92197D0A6547B44A1567814F851FA687E1C@LEMBU.sumatrasoftware.com>
A modest proposal: could those people attaching files please give them
a content-type of "text/plain" rather than "application/binary"?
They'd still be transmitted faithfully, bus mailers could display them
inline.
Thanks,
Andrew.
next prev parent reply other threads:[~2004-10-12 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 9:35 Jeroen Frijters
2004-10-12 9:41 ` Andrew Haley [this message]
2004-10-12 9:41 ` Michael Koch
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=16747.42661.267373.605540@cuddles.cambridge.redhat.com \
--to=aph@redhat.com \
--cc=classpath@gnu.org \
--cc=mauve-discuss@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).