From: Lee Willis <lee@gbdirect.co.uk>
Subject: Re: Broken patches due to MML
Date: 03 Dec 1998 10:28:12 +0000 [thread overview]
Message-ID: <lz90gp4j0j.fsf@landlord.gbdirect.co.uk> (raw)
In-Reply-To: <wsg1ayscas.fsf@orcus.priv.at>
Robert Bihlmeyer <robbe@orcus.priv.at> writes:
> sometimes it is really necessary to include the unspeakable
> less-than-hash-part sequence verbatim. For example gnus patches:
> The 0.56 patch sent over ding-patches@gnus.org was broken, because MML
> munged any occurances of the forbidden word into MIME separators.
Yeah, and here was me thinking it was me that was broken :)
> Is this brokenness in MML, the send-patch-mechanism, or both?
send-patch-mechanism (See below)
> Is there a way to quote this? Does message automatically quote any
> occurances inside a part I insert?
There is a way to quote the part thingies which I can't actually
remember at the moment, and no message doesn't automatically quote them
because it is perfectly legal for you to manually insert a part
definition. Therefore we're left with option b) Lars' send patch is
broken as it should really look for and correctly quote the part things
in patches. Still since he's given us pretty characters and pictures
I'll let him off ;)
Lee.
--
I was doing object-oriented assembly at 1 year old ...
For some reason my mom insists on calling it "Playing with blocks"
next prev parent reply other threads:[~1998-12-03 10:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-02 17:07 Robert Bihlmeyer
1998-12-03 10:28 ` Lee Willis [this message]
1998-12-03 13:07 ` Robert Bihlmeyer
1998-12-04 0:53 ` 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=lz90gp4j0j.fsf@landlord.gbdirect.co.uk \
--to=lee@gbdirect.co.uk \
/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).