To: Mark Walters <markwalters1009@gmail.com>, notmuch@notmuchmail.org
Subject: Re: Exporting mime email
In-Reply-To: <87k455p1mj.fsf@qmul.ac.uk>
References: <87hb09y8p8.fsf@qmul.ac.uk>
	<cunehvd44a8.fsf@hotblack-desiato.hh.sledj.net>
	<87k455p1mj.fsf@qmul.ac.uk>
User-Agent: Notmuch/0.10.2+151~gbf1dc2b (http://notmuchmail.org)
	Emacs/24.0.92.1 (x86_64-pc-linux-gnu)
From: David Edmondson <dme@dme.org>
Date: Fri, 06 Jan 2012 10:39:43 +0000
Message-ID: <cuny5tl2jyo.fsf@hotblack-desiato.hh.sledj.net>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"
Precedence: list

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On Fri, 06 Jan 2012 10:27:16 +0000, Mark Walters <markwalters1009@gmail.com=
> wrote:
> Does saving the message like this give you a file you can apply directly
> with the patch command? When I save it (using | or from view-raw) I get
> a message which looks like

Ahh. This particular message is a bad example for me to check, because I
have the version that I bcc'd rather than the one delivered by the
mailing list.

Presumably something is converting it from 8bit to base64 along the
path.

I scouted around for other messages that include =C2=A9 (which is what I
presume causes the encoding), but the ones I have are all still 8bit.

> I have just discovered git am which solves this problem for patches but
> I think it might be useful to be able to export the plain-text email
> sometimes.

Agreed.

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk8Gz28ACgkQaezQq/BJZRb3DQCggsurSGRdcQrFobqXnK7tEfXl
/n4An1dNg4dj6GwTjkJU9JrVl1UVqdwq
=z3EG
-----END PGP SIGNATURE-----
--=-=-=--