mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesper Juhl <jesper.juhl@gmail.com>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org, arjan@infradead.org
Subject: Re: [PATCH 0/4] pmap
Date: Sun, 22 Jan 2006 23:52:52 +0100	[thread overview]
Message-ID: <9a8748490601221452j41491984j6da14fa53ba9af55@mail.gmail.com> (raw)
In-Reply-To: <200601222215.k0MMFOYD213932@saturn.cs.uml.edu>

On 1/22/06, Albert D. Cahalan <acahalan@cs.uml.edu> wrote:
>
[snip]
>
> I found an old email account that still supports adding raw binay data
> to an email message body. I really wish we could get away from this,

1. having patches inline in messages instead of as attachments make
initial viewing of the patches much easier - no need to open a
sepperate attachment just to review a patch.
2. Commenting on patches is a lot easier when you can just reply to
the message and have the patch quoted inline and then add your
comments.
3. saving patches for application is easy when you can just save the
email message with the patch inline - then you have the explanation of
the patch and the patch itself nicely contained in a single file (and
patch will conveniently strip the extra text before the patch-proper
when you apply it).
4. You don't need an account that's able to add 'binary data' -
patches should preferable be in 7-bit ASCII text form, not 8-bit.

And if your current MUA doesn't allow you to add text files inline,
then there are several that do - mutt, pine & kmail come to mind and
there are several others.

> because it makes contributions damn near impossible for some people.
> Other people are far worse off than I am.
>
I'm currious - in what situations are you prevented from sending
patches inline in emails??


--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

  reply	other threads:[~2006-01-22 23:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-22 22:15 Albert D. Cahalan
2006-01-22 22:52 ` Jesper Juhl [this message]
2006-01-22 23:34 ` Randy.Dunlap

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=9a8748490601221452j41491984j6da14fa53ba9af55@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=acahalan@cs.uml.edu \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®