Re: C++ PATCH: Tree dumper

[Alexandre Oliva <aoliva at redhat dot com>]

On Nov 21, 2001, Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> wrote:

> On 20 Nov 2001, Geoff Keating wrote:
>> I think what was intended is that if patches are sent as MIME
>> sections, they should be:
>> 
>> 1. Marked with a content-disposition of 'inline', not 'attachment'; and
>> 2. Encoded as '7bit' or '8bit', not 'base64' or 'quoted-printable'.
>> 
>> I believe the aim is to allow those who don't have MIME-capable mail
>> readers to still be able to read the patch without needing to run a
>> separate decoder, and those who do have MIME-capable mail readers to
>> have the patch in the body of the mail where they can most
>> conveniently quote it in replies.

> Alexandre, I believe Geoff summed this up nicely, so we do not need to
> have special rules for your targets, but should clarify that page. Would
> you mind doing so?

Sorry about the long delay.

> (For the web pages also MIME attachments are fine with me.)

I'd rather go with a uniform set of rules.  Would you *prefer* to get
patches as MIME attachments, or are the guidelines below ok with you?

Ok to install?

Index: contribute.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/contribute.html,v
retrieving revision 1.41
diff -u -p -c -r1.41 contribute.html
cvs server: conflicting specifications of output style
*** contribute.html	2001/11/28 23:24:24	1.41
--- contribute.html	2001/12/02 21:33:33
*************** changes easier but do not change GCC's b
*** 120,128 ****
  the changes that actually make use of the new code and change GCC's
  behavior.)</p>
  
! <p>We accept patches as plain text (preferred for the compilers
! themselves), MIME attachments (preferred for the web pages), or as
! uuencoded gzipped text.</p>
  
  <p>When you have all these pieces, bundle them up in a mail message
  and send it to <a
--- 120,135 ----
  the changes that actually make use of the new code and change GCC's
  behavior.)</p>
  
! <p>We accept patches as plain text or as MIME parts of type
! <code>text/x-patch</code> or <code>text/plain</code> (not
! <code>application/</code><i>whatever</i>), disposition
! <code>inline</code> (not <code>attachment</code>), encoded as
! <code>7bit</code> or <code>8bit</code> (not as <code>base64</code> or
! <code>quoted-printable</code>).  If the patch is too big or too
! mechanical, posting it gzipped or bzip2ed, uuencoded or as a
! <code>base64</code> attachment is acceptable, as long as the ChangeLog
! is still posted as plain text.  Avoid MIME large-message splitting
! (<code>message/partial</code> at all costs.</p>
  
  <p>When you have all these pieces, bundle them up in a mail message
  and send it to <a


-- 
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