X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=ge4xOHxXqp58CTtwv2e+vzPj041mu
	YzdQv8btfBCDhTMnT/gf60OS60cQjwqnl3kNdMZazuf4mbEeyWZ1o8c9yrnuJzE3
	citj3vTG/lUMdhWo3kPbN8Bpntb5EABFosEwnr8qDFoVMNiMNdD2rkff44Gcc/U/
	T7Z/ERlEGxTDvA=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; s=default; bh=SEOj7Knb+LyR9KGMXJiYaXeWooo=; b=dF5
	A0wVOls6uPsc3vRjkdQH4/7E5rC9iIm4p7Naf+tH1XPrhCgDAjgpIZWaqsvlJB8C
	nUGCuXKjUFVpb+TDTXiqjW+rvKVH69i72nIIt1nuZL0nYy7B/xS1nx6usTDs8Cdm
	WdgfXOyqyQTXHO/DVRktJEK7WVs09Vh0TpbTYW4Q=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-0.1 required=5.0 tests=AWL,BAYES_00,MIME_BASE64_BLANKS,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS autolearn=ham version=3.3.2
X-HELO: na01-by2-obe.outbound.protection.outlook.com
From: "Habermann, Dave (DA)" <DAHabermann@dow.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.33-0.1
Date: Tue, 28 Oct 2014 17:07:18 +0000
Message-ID: <C9D37D92E903B347A31B9CF82643BA2807300F25@046-CH1MPN1-043.046d.mgd.msft.net>
References: <announce.20141022092323.GH32374@calimero.vinschen.de> <C9D37D92E903B347A31B9CF82643BA28072F9229@046-CH1MPN1-043.046d.mgd.msft.net> <20141022135424.GB18857@calimero.vinschen.de> <C9D37D92E903B347A31B9CF82643BA28072FFFD5@046-CH1MPN1-043.046d.mgd.msft.net> <20141027212637.GZ20607@calimero.vinschen.de> <C9D37D92E903B347A31B9CF82643BA2807300C63@046-CH1MPN1-043.046d.mgd.msft.net> <20141028142021.GL20607@calimero.vinschen.de>
In-Reply-To: <20141028142021.GL20607@calimero.vinschen.de>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
X-OrganizationHeadersPreserved: 046-CH1MMR1-005.046d.mgd.msft.net
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report:	CIP:65.52.44.158;CTRY:US;IPV:NLI;EFV:NLI;SFV:NSPM;SFS:(10009020)(6009001)(428002)(189002)(199003)(5423002)(85306004)(93886004)(6806004)(22756005)(85852003)(87936001)(46102003)(80022003)(22746005)(2656002)(50466002)(99396003)(33656002)(86146001)(120916001)(4396001)(77096002)(23676002)(84676001)(104016003)(55846006)(92726001)(86362001)(92566001)(110136001)(69596002)(101416001)(68736004)(54356999)(76176999)(44976005)(50986999)(21056001)(106116001)(20776003)(105586002)(47776003)(107886001)(76482002)(97736003)(66066001)(2351001)(107046002)(31966008)(2501002)(106466001)(95666004)(64706001)(81156004)(79686002);DIR:OUT;SFP:1101;SCL:1;SRVR:BY2PR0101MB0872;H:mail.bsnconnect.com;FPR:;MLV:sfv;PTR:InfoDomainNonexistent;MX:1;A:1;LANG:en;
X-CrossPremisesHeadersPromoted: BL2FFO11FD013.protection.gbl
X-CrossPremisesHeadersFiltered: BL2FFO11FD013.protection.gbl
X-Microsoft-Antispam: UriScan:;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:BY2PR0101MB0872;
X-Forefront-PRVS: 0378F1E47A
Received-SPF: None (protection.outlook.com: dow.com does not designate permitted sender hosts)
Authentication-Results: spf=none (sender IP is 65.52.44.158) smtp.mailfrom=DAHabermann@dow.com;
X-OriginatorOrg: dow.com
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id s9SH7gbk003243

>> should be created.  I would think that some instructions in the docs
>> near the statement mentioned above would be more than sufficient,
>> since this is a "fine tuning" sort of thing.

> Agreed.  Do you have some idea how to phrase this?  I'd be grateful
> for a nice two or three paragraphs discussing this.

Will do, but it will take me a bit as I'd like to make sure I've got 
it right, plus I've got some "day job interference" for the next day
or so.

