From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: jimb@red-bean.com, gdb-patches@sources.redhat.com
Subject: Re: RFA: Building GDB under GLIBC 2.8
Date: Sun, 14 Dec 2008 21:54:00 -0000 [thread overview]
Message-ID: <8ac60eac0812141353h3b8336e8la6a73a4e6aa2fa4c@mail.gmail.com> (raw)
In-Reply-To: <200812141956.mBEJuoDq010551@brahms.sibelius.xs4all.nl>
On Sun, Dec 14, 2008 at 11:56 AM, Mark Kettenis <mark.kettenis@xs4all.nl> wrote:
>> Date: Sat, 13 Dec 2008 22:07:29 -0800
>> From: "Jim Blandy" <jimb@red-bean.com>
>>
>> > Jim, could you please try sending diffs such that they are readable in
>> > a text-based mail reader?
>>
>> I'm afraid gmail will mangle them if I don't include them as
>> attachments.
Gmail will actually do text/plain attachment with 7-bit encoding
if the attached filename ends in .txt
However, it appears that there is some other message rewriting
happening elsewhere, because my messages with text/plain/7-bit
attachments end up as text/plain/base64 by the time they reach
sourceware.org :-(
>> MIME attachments have been in widespread use for a very
>> long time; does your mail reader have difficulty displaying them?
>
> Ugh, web-based email. I keep wondering how people can write anything
> but three-line mails with those. I must be getting old...
There is an "It's all text" firefox plugin, which makes editing
the messages with a real editor easy. Unfortunately, whitespace
and line wrapping are still a problem.
> Anyway, I use emacs's rmail to read my mail. Have been for years, and
> for me being able to have my mail inside my editor is fairly
> essential. Rmail isn't MIME-aware, which is great. I don't get to
> see most of the random crap that uneducated computer users attach to
> their mails. And if I really want to look at it, there's etach wich
> detaches MIME attachments from my mail and saves them as a file.
>
> Detaching attachments is fine for most things, but it is really
> annoying for reviewing patches, since in many cases you want to make
> remarks about particular lines of a patch, whcih is best done in line.
Surely you can open the detached attachment in another buffer and
cut/paste the lines you want to comment on back into the reply?
> This is the reason why we used to have the (unwritten?) rule that
> patches were supposed to be sent inline using a mail client that
> didn't muck with the contents of the mail message.
Yes, I would very much like such a client. For a long time I've
used emacs VM mode, but there are several features of Gmail which
I do not know how to emulate in emacs-VM, so it isn't really
feasible for me to switch back to emacs :(
Base64 attachments appear not to cause too much trouble in this
list (you are the only one who complained recently), although
they are not tolerated in glibc lists.
Cheers,
--
Paul Pluzhnikov
next prev parent reply other threads:[~2008-12-14 21:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-13 2:05 Jim Blandy
2008-12-13 20:33 ` Mark Kettenis
2008-12-13 23:02 ` Andreas Schwab
2008-12-14 6:08 ` Jim Blandy
2008-12-14 19:57 ` Mark Kettenis
2008-12-14 21:54 ` Paul Pluzhnikov [this message]
2008-12-14 18:26 ` Jan Kratochvil
2008-12-14 18:26 ` RFA: Building GDB under GLIBC 2.8 [resend w/the patch] Jan Kratochvil
2008-12-15 9:02 ` RFA: Building GDB under GLIBC 2.8 Jim Blandy
2008-12-15 20:07 ` Tom Tromey
2008-12-15 20:17 ` Pedro Alves
2008-12-20 0:46 ` Jim Blandy
2008-12-29 5:50 ` Joel Brobecker
2008-12-29 23:48 ` Tom Tromey
2009-01-06 18:32 ` Jim Blandy
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=8ac60eac0812141353h3b8336e8la6a73a4e6aa2fa4c@mail.gmail.com \
--to=ppluzhnikov@google.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@red-bean.com \
--cc=mark.kettenis@xs4all.nl \
/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