Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Thu, 7 Dec 2000 09:56:01 -0500
Message-Id: <200012071456.JAA03784@envy.delorie.com>
X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f
From: DJ Delorie <dj AT delorie DOT com>
To: tailbert AT yahoo DOT com
CC: cygwin-developers AT sources DOT redhat DOT com
In-reply-to: <FMEOJCMLNIMPBKAPFPIHCEFCCFAA.tailbert@yahoo.com>
Subject: Re: doctool.c patch
References:  <FMEOJCMLNIMPBKAPFPIHCEFCCFAA DOT tailbert AT yahoo DOT com>


> PS. In future, do you prefer attachments or do you just patch from the mbox
> file?

If your mailer can send attachments without corrupting them
(converting tabs to spaces, wrapping lines), just including the text
within the message is best, because then we can patch directly from
the mbox file.  However, if you send as a MIME attachment, we can deal
with those also - it just requires an extra step to decode them.
At least, that's *my* preference ;-)