From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org,
Paul Pluzhnikov <ppluzhnikov@google.com>,
Eli Zaretskii <eliz@gnu.org>,
sergiodj@linux.vnet.ibm.com
Subject: Re: [RFA] Fix "show convenience" test
Date: Thu, 17 Sep 2009 19:25:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0909171923510.5988@digraph.polyomino.org.uk> (raw)
In-Reply-To: <200909171916.44937.pedro@codesourcery.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 943 bytes --]
On Thu, 17 Sep 2009, Pedro Alves wrote:
> On Thursday 17 September 2009 18:57:31, Paul Pluzhnikov wrote:
> > <quote>
> >
> > *sigh*
> >
> > How old is base64 now, has it hit 15 years yet? "text based mail reader"
> > my left foot, there's nothing to prevent a text based mail reader from
> > decoding mail in a 15 year old standard.
> >
> > I can accept the argument that a pure text, 7bit ascii message of a
> > text subtype shouldn't be encoded automatically. I'm even suprised
> > that its base64 encoded and not qp-encoded if there happened to be
> > line-ending/wrapping concerns.
> >
>
> I hope that means that they'll address it. :-) This also prevents
> mail archives from showing the patch inline. Compare:
It's a bug in the mail archiving software if it decides that based on
Content-Transfer-Encoding rather than Content-Disposition.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2009-09-17 19:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 0:32 Sérgio Durigan Júnior
2009-09-16 13:16 ` Pedro Alves
2009-09-16 17:08 ` Eli Zaretskii
2009-09-17 16:37 ` Paul Pluzhnikov
2009-09-17 17:26 ` Eli Zaretskii
2009-09-17 17:57 ` Paul Pluzhnikov
2009-09-17 18:16 ` Pedro Alves
2009-09-17 18:29 ` Paul Pluzhnikov
2009-09-17 19:25 ` Joseph S. Myers [this message]
2009-09-17 19:52 ` Pedro Alves
2009-09-17 18:26 ` Eli Zaretskii
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=Pine.LNX.4.64.0909171923510.5988@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=ppluzhnikov@google.com \
--cc=sergiodj@linux.vnet.ibm.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