Date: Tue, 11 Oct 2011 13:26:18 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: stdio.h: broken standard compliance.
Message-ID: <20111011172618.GB4522@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <82593b31494b784ab45fc7915f0e3435 AT 127 DOT 0 DOT 0 DOT 1>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <82593b31494b784ab45fc7915f0e3435@127.0.0.1>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Mon, Oct 10, 2011 at 09:58:50PM -0700, Kaz Kylheku wrote:
>Christopher Faylor writes:
>> The convention in this mailing list is that you read the mailing list.
>I see now from the archives that this list is configured
>to generate the unfortunate Reply-to header, which by many
>is considered a mailing list misconfiguration.

The cygwin mailing list does not set Reply-To.  It does set
"Mail-Followup-To".

>[[ Apologies to Corinna: I understand now that you fell
>victim to this Reply-to trap! Argh! ]]

I'm sure that Corinna actually knew just what she was doing.

[rest of message snipped since it was based on an incorrect
assumption]

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple