Re: none

[Alexandre Oliva <aoliva@redhat.com>]

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

> On 2 Dec 2001, Alexandre Oliva wrote:
>>> (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?

> I'm pragmatic, so let's go with a uniform set of rules. ;-)

Thanks

>> Ok to install?

> Could we have two sentences, as in "This and this and this is fine.
> This and this and this is not fine" instead of "This is fine  (while
> this is not fine) and this is fine (while this is not fine)"?

> I believe it's easier to read and understand what we want that way
> -- and the patch is fine with this change.

Thanks, I'm checking this in:

Index: contribute.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/contribute.html,v
retrieving revision 1.42
diff -u -p -c -r1.42 contribute.html
cvs server: conflicting specifications of output style
*** contribute.html	2001/12/10 10:27:44	1.42
--- contribute.html	2002/01/02 02:40:31
*************** 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,137 ----
  the changes that actually make use of the new code and change GCC's
  behavior.)</p>
  
! <p>We prefer patches posted as plain text or as MIME parts of type
! <code>text/x-patch</code> or <code>text/plain</code>, disposition
! <code>inline</code>, encoded as <code>7bit</code> or
! <code>8bit</code>.  If the patch is too big or too mechanical, posting
! it gzipped or bzip2ed and uuencoded or encoded as a
! <code>base64</code> MIME part is acceptable, as long as the ChangeLog
! is still posted as plain text.  Other than that, it is strongly
! discouraged to post patches as MIME parts of type
! <code>application/</code><i>whatever</i>, disposition
! <code>attachment</code> and/or encoded as <code>base64</code> or
! <code>quoted-printable</code>.  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


>> ! Avoid MIME large-message splitting (<code>message/partial</code> at
>> ! all costs.</p>

> I have not seen message/partial in the wild yet, so I think we could
> omit this, but if you tell me that you worry about it, I will believe
> you. :-)

I do.  I've seen it before, and it's often annoying to read it even
if your mail reader supports message/partial.  Not to mention the
disruptive effect to the archives.

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