From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: linux-mtd@lists.infradead.org
Subject: Re: [PATCH 3/4] util/jffs2reader catfile fix
Date: Mon, 24 Oct 2005 11:39:30 +0200 [thread overview]
Message-ID: <200510241139.30533.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <4359cf33.4d2108c5.1cab.ffff918e@mx.gmail.com>
> The patch without quoted-printable encoding and extra linebreaks.
> Thanks.
You'll save a lot of trouble if you do NOT inline the patch, but attach it as
a file. That will create a MIME encoded e-mail that is understood since about
8 years by about every e-mail program. Attachments are MEANT to be
byte-transparent :-)
Surely even GMAIL allows you to attach a file, maybe via a button in the web
formular?
next prev parent reply other threads:[~2005-10-24 9:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-15 3:13 [PATCH 3/4] util/jffs2reader catfile fix Suzuki Takashi
2005-10-22 5:33 ` Suzuki Takashi
2005-10-24 9:39 ` Holger Schurig [this message]
2005-10-24 11:20 ` Jörn Engel
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=200510241139.30533.hs4233@mail.mn-solutions.de \
--to=hs4233@mail.mn-solutions.de \
--cc=linux-mtd@lists.infradead.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