Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Fri, 1 Sep 2000 16:57:44 -0400 Message-Id: <200009012057.QAA24018@envy.delorie.com> From: DJ Delorie To: cwilson AT ece DOT gatech DOT edu CC: cygwin AT sources DOT redhat DOT com In-reply-to: <39B016D9.3B1B5DE1@ece.gatech.edu> (message from Charles Wilson on Fri, 01 Sep 2000 16:51:37 -0400) Subject: Re: Instructions for submitting patches References: <200009012048 DOT QAA23916 AT envy DOT delorie DOT com> <39B016D9 DOT 3B1B5DE1 AT ece DOT gatech DOT edu> > gzipped and uuencoded, then pasted into the email is not good? No, unless your mailer will corrupt them otherwise. If you encode or attach them, instead of just pasting them, then I can't just hit (R)eply to comment on them, and I can't read them in my mailer - I have to save them to disk first, then bring them up in a separate editor, then paste them back into the mailer to comment on them. If your "file attach" function attaches them as plain 8-bit unencoded text (not base64 or quoted-printable), that's acceptable, because MIME basically leaves it as unchanged text. It's harder to read when mimeified, but I can still actually read it in the mailer. Perhaps you have some strange belief that I apply patches without actually *reading* them first? ;-) -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com