From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: pedro@codesourcery.com, sergiodj@linux.vnet.ibm.com,
gdb-patches@sourceware.org
Subject: Re: [RFA] Fix "show convenience" test
Date: Thu, 17 Sep 2009 17:57:00 -0000 [thread overview]
Message-ID: <8ac60eac0909171057j6c6ac9e3neb5f46912b10efe9@mail.gmail.com> (raw)
In-Reply-To: <83iqfhwkhh.fsf@gnu.org>
On Thu, Sep 17, 2009 at 10:26 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> The attachment was actually text, just base64-encoded:
>
> Lately, my eyes lost their ability to read base64 without help ;-)
You appear to be using emacs; surely it can help?
I've used VM in the past, and had no problems decoding base64 (or anything
else for that matter).
BTW, here is a response from gmail folks to my request to be able to send
text/plain attachments.
<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.
</quote>
>> How does the attached patch look?
>
> It's fine now, thanks.
So committed.
Thanks,
--
Paul Pluzhnikov
next prev parent reply other threads:[~2009-09-17 17:57 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 [this message]
2009-09-17 18:16 ` Pedro Alves
2009-09-17 18:29 ` Paul Pluzhnikov
2009-09-17 19:25 ` Joseph S. Myers
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=8ac60eac0909171057j6c6ac9e3neb5f46912b10efe9@mail.gmail.com \
--to=ppluzhnikov@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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