From: Laura Conrad <lconrad@world.std.com>
Subject: bug report: [Han-Wen Nienhuys <hanwen@cs.uu.nl>] patch to abc2ly
Date: 27 Aug 1999 09:12:57 -0400 [thread overview]
Message-ID: <m37lmhtlie.fsf@serpent.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 379 bytes --]
I just sent a patch to another mailing list, via the "Attach file as
mime" menu item in xemacs, pgnus 0.95. The maintainer is getting a
mime error.
Attached are his message with all his headers and the message I
sent (also attached via the menu).
I used the default application/octet-stream; would it have helped if I
had used something more specific? (It was a .gz file.)
[-- Attachment #2: Type: message/rfc822, Size: 1822 bytes --]
From: Han-Wen Nienhuys <hanwen@cs.uu.nl>
To: Laura Conrad <lconrad@world.std.com>
Subject: patch to abc2ly
Date: Fri, 27 Aug 1999 14:46:05 +0200 (CEST)
Message-ID: <14278.34957.146212.169896@dokkum.cs.uu.nl>
lconrad@world.std.com writes:
> Attached is a patch, with a couple of quick fixes that make abc2ly
> more useful to me:
I get
MIME error: "something other than line break or hex digits after = in quoted-printable encoding"
Can you send it in plaintext?
--
Han-Wen Nienhuys, hanwen@cs.uu.nl ** GNU LilyPond - The Music Typesetter
http://www.cs.uu.nl/people/hanwen/lilypond/index.html
[-- Attachment #3: message including error-producing MIME --]
[-- Type: application/octet-stream, Size: 4371 bytes --]
[-- Attachment #4: Type: text/plain, Size: 151 bytes --]
--
Laura (mailto:lconrad@world.std.com , http://www.world.std.com/~lconrad/ )
(617) 661-8097 fax: (801) 365-6574
233 Broadway, Cambridge, MA 02139
next reply other threads:[~1999-08-27 13:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-27 13:12 Laura Conrad [this message]
1999-08-27 19:12 ` Kai Großjohann
1999-09-25 6:34 ` Lars Magne Ingebrigtsen
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=m37lmhtlie.fsf@serpent.local \
--to=lconrad@world.std.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 NNTP newsgroup(s).