From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: [9fans] how could i've missed this one?
Date: Wed, 10 Mar 2004 22:37:33 -0700 [thread overview]
Message-ID: <e351c6231aafae2be417a9fce16b5a2b@plan9.ucalgary.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 249 bytes --]
this is really silly -- only after pulling all the new unknowns did I
realize that .bg isn't there!
attached in this message is the bulgarian flag, to be added as
48x48x8/u/unknown.bg (.dict entry: "bg/unknown u/unknown.bg")
thanks, andrey
[-- Attachment #2.1: Type: text/plain, Size: 306 bytes --]
The following attachment had content that we can't
prove to be harmless. To avoid possible automatic
execution, we changed the content headers.
The original header was:
Content-Type: application/octet-stream
Content-Disposition: attachment; filename=unknown.bg
Content-Transfer-Encoding: base64
[-- Attachment #2.2: unknown.bg.suspect --]
[-- Type: application/octet-stream, Size: 363 bytes --]
next reply other threads:[~2004-03-11 5:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 5:37 andrey mirtchovski [this message]
2004-03-11 5:43 ` andrey mirtchovski
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=e351c6231aafae2be417a9fce16b5a2b@plan9.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).