C++ PATCH: Tree dumper

[Alexandre Oliva]

On Nov 20, 2001, Mark Mitchell <mark@codesourcery.com> wrote:

>> I was not aware of a policy on whether or not to send patches as a
>> separate MIME part; I have been doing so for a while, using the MIME type
>> text/x-patch.

> http://gcc.gnu.org/contribute.html:

>   We accept patches as plain text (preferred for the compilers
> themselves),  MIME attachments (preferred for the web pages), or as
> uuencoded gzipped
>   text.

MIME sections != MIME attachments.  A MIME section can be either
inline or an attachment.  Also, a MIME section can be of types text,
application, audio, video or perhaps some other types I'm missing.
Each type has a number of sub-types, some standard, some standard
extensions.  text/x-patch is a common extension.  If you post
something as an inline MIME section of type text/x-patch, you're
posting it as plain text, just as requested.

Now, if by `plain text', whoever came up with that text in
contribute.html meant to ban MIME sections in general, I'd rather see
this policy revised, especially now that the mailing list archives
will let you download MIME sections separately.  If we can't agree on
accepting MIME sections at all for patches in general, I'd like to add
some HTML code explaining exactly what we mean by plain text and MIME
attachments, and an exception to patches for SH, MN10300 and
configury, that I'd much rather see in the form of MIME sections.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me