Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-ID: <39B02137.7A8AE167@ece.gatech.edu>
Date: Fri, 01 Sep 2000 17:35:51 -0400
From: Charles Wilson <cwilson@ece.gatech.edu>
MIME-Version: 1.0
To: DJ Delorie <dj@delorie.com>
CC: cygwin@sources.redhat.com
Subject: Re: Instructions for submitting patches
References: <VA.000004d4.016577bf@thesoftwaresource.com> <200009012048.QAA23916@envy.delorie.com> <39B016D9.3B1B5DE1@ece.gatech.edu> <200009012057.QAA24018@envy.delorie.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

DJ Delorie wrote:
> 
> > 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.

Oh, ok.  Most other mailing lists specify gz.uue, so I just assummed...I
mean, a .gz.uue message is virtually guaranteed to arrive in exactly the
same form as it was transmitted -- no tab->space stuff, no line
wrapping, quoted-printable-munging, etc.

That's the upside. The downside is just as you say: you can't 'reply' or
comment on parts of the patch, without lots of gymnastics.

> 
> Perhaps you have some strange belief that I apply patches without
> actually *reading* them first?  ;-)

No, of course not. I just thought you did it the hard way. 

--Chuck

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com