This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: requiring text format for patch attachments?
- From: Paul Eggert <eggert at cs dot ucla dot edu>
- To: Roland McGrath <roland at hack dot frob dot com>
- Cc: GLIBC Devel <libc-alpha at sourceware dot org>
- Date: Sat, 29 Jun 2013 01:30:30 -0700
- Subject: Re: requiring text format for patch attachments?
- References: <CABXK9nfhHHnm+4LLnrtW-=Py69WvwcF3BWt-kf-TNHsPvqa5ig at mail dot gmail dot com> <51CD9D3B dot 8090002 at tilera dot com> <51CDDD8D dot 9010104 at systemhalted dot org> <51CDE1BE dot 2020501 at tilera dot com> <51CDFB6F dot 5020700 at cs dot ucla dot edu> <51CE03AC dot 4090300 at redhat dot com> <20130628215050 dot 2D8382C09C at topped-with-meat dot com>
On 06/28/2013 02:50 PM, Roland McGrath wrote:
> It's the strong preference that people not use attachments.
OK, thanks, I changed the text so that it now reads as follows.
* The strong preference is that you include the patch as part of
the text of the email. However, if your mailer unavoidably
wraps long lines or otherwise alters patch contents, or if the
diff might cause problems due to binary data or mixed
encodings, attach the patch to the email. The attachment
should normally employ a Content-Type of text/x-diff or
text/x-patch (or at least text/plain) and a charset of UTF-8 or
US-ASCII; if it contains binary data or mixed encoding it may
need to specify a Content-Type of application/octet-stream
instead. Please use an attachment file name that ends in
".diff" or ".patch" (or at least ".txt").