C++ PATCH: Tree dumper

[Jason Molenda]

Geoff wrote:

> 1. Marked with a content-disposition of 'inline', not 'attachment'; and

I suspect most MUAs don't make this easy for users to do.  Maybe
I can do it with mutt, but it's not clear how I'd go about it.
And I've been using mutt for a very long time...

Besides which, our wonderful web archives (All Hail Mhonarc) will
decode and save aside any attachment with a disposition of attachment
into a text file.  Very tasty indeed.  Bring up your browser on
that file and you'll have pure, unabashed patchy goodness.  (before 
Nov 12th, you'd get HTML <PRE> goodness, which isn't really as good,
but better than nothing.  The new setup is more useful.)

I also recently snuck in a little feature to the web archives so that
plain text versions of mail messages are available for all notes for
easy feeding to patch...  unless you're using a Content-Encoding
other than 7bit.  Which brings us to,

> 2. Encoded as '7bit' or '8bit', not 'base64' or 'quoted-printable'.

I may be wrong on this, but I think this will conflict with the
way some MUAs deal with non-ASCII langs.  For instance, Andreas
Schwab sends e-mails with a charset of iso-8859-15 and his
Content-Transfer-Encoding is quoted-printable.  We could blame this
on his MUA or on his language :-), but MIME is hidden from most
users and expecting people to understand what their MUA is doing
under the covers doesn't seem too useful.

I think anything stronger than "Guidance for posting patches in
MIME mail notes" is going to cause flame wars as people innocently
violate the rules.

Jason