From: Andreas Schwab <schwab@linux-m68k.org>
To: ding@gnus.org
Subject: Re: Message mangled
Date: Fri, 28 Jan 2011 20:26:53 +0100 [thread overview]
Message-ID: <m2fwscn81u.fsf@igel.home> (raw)
In-Reply-To: <87y66529dk.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 27 Jan 2011 15:51:35 -0800")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> On 20 Jan 2011, at 22:01, Ludovic Court=E8s wrote:
>>
>>> Can you post the exact link command line and error message?
>>
>> $ make
>> gcc parser.o lexer.o driver.o guile++.o guile.o exception.o tuple.o =20
>> `guile-config link` -lstdc++ -o guile++
>
> [...]
>
>> But the trailing ‘=20’ and the leading backquote on the next line get
>> swallowed, and a newline is inserted there.
>
> Well, the content-transfer-encoding is obviously quoted-printable, which
> is why the =20 is, er, decoded. But the ` being swallowed is odd.
The article is also format=flowed which adds another decoding layer.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2011-01-28 19:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 10:26 Ludovic Courtès
2011-01-27 23:51 ` Lars Ingebrigtsen
2011-01-28 19:26 ` Andreas Schwab [this message]
2011-01-28 22:11 ` Lars Ingebrigtsen
2011-01-31 20:30 ` Ludovic Courtès
2011-02-01 2:37 ` Lars 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=m2fwscn81u.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).