X-Recipient: archive-cygwin AT delorie DOT 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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=hmwdNuW5Tpj5yKvbSWKqtzkUG9Qq0EuP5OnGvWhYx4e
	Y2mAMVjrDMM7FHBfk5H0WzNH9T8V5H7kNacbkNhtisHvm6WeSt+tf9ajU5gAw6Mc
	2zc1P5DSRCE1qcu4/0+QIBhyd8Xrs5E8refFRaQ5XRG1ajI5CnROHtTnV5iqB6DQ
	=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=bP3D0LXoM5SMg9xRnv4/m5sN3/Y=; b=QROuSal5Z/RKH3zOd
	QD40FKjYpSzuZUr+w9A3X548Z0d4OPqIrTsODYa8/EOQS09A9HPwpZNhZVqdSSc/
	YICYsVrHN8MRXNmTPZ9mjpVhs8YBON9CsOgd5L8IU2+XaFCggCW6KvNbWE4qms5e
	sS3JiCZmmocpYKE9dBbkpyoZA8=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=1.8 required=5.0 tests=BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2
X-HELO: mout.kundenserver.de
Message-ID: <558EC861.2030903@towo.net>
Date: Sat, 27 Jun 2015 17:59:29 +0200
From: Thomas Wolff <towo AT towo DOT net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: mintty system integration before release
References: <558EA4BB DOT 8080506 AT towo DOT net> <20150627145021 DOT GA23036 AT calimero DOT vinschen DOT de>
In-Reply-To: <20150627145021.GA23036@calimero.vinschen.de>
X-TagToolbar-Keys: D20150627175929717
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-UI-Out-Filterresults: notjunk:1;V01:K0:SzCOv3G0MAQ=:77FZ2ZrFzcyic55UAInXid P46qMbrnhkopxZD/GZFTC6pKcGmMWz3Z++A3B9INNDIooNz4i22TUUMX0ColmaSiFIdgwet9A 3MQiCq+o+3ELztxzdm8pePYKr2ySqmeadYslI2GRLsO+JCv/t10+1RvSM11RXPeLKMJ798z09 nNvijZcOF5uWsHP6UIvLk4giTZ+Uz0jXJgu7cRtpqBoe+23dwVmUBwSP0eKOYxDYpXfi14/JI uO2KO+m644J4e74fijR3M62mabqHCqgSzIYSd3RIVB70/fUKPZxZndxMkBTK6olGaFMOIKHUJ 7p4TEJ/6vrYkwXq5mpE6qcNpbFRphfOMwaqwQgdzl+03cUXuOPFsgDLZtfNo09GwqppD4G1Rv NJLzNWa4FF0UDjeyv/cVbIVWw0x+6mL2/Dj5b+IG9BEm9dDir55TlasIW5JDjyqhzrK6CktdN +YXpcIOrxlJeVbRjfpPGQsCV+O4H6WXRnWSUAvRABjQN0Wz5JySUUB3tDQd6c5CddBJcR10HA 16HVWNiAe1n0s9qhv7NR/9OE6DK7U5nD7cXTOVzzgd9A2o9s7fUgCpkYdtgba6cJNz1Zeic74 PxsHPAIGU+TOiM8cpVqkTpIYgcPoXxZ55yPKLxsa6vk7sAnVE9leFuaewEu9hB+OFEC0taFDL p4zhsFmSwr1FT6ZLwtA0HpDLpDI2iZcWsPKXvr63+9GE8Ww==
X-IsSubscribed: yes

Am 27.06.2015 um 16:50 schrieb Corinna Vinschen:
> On Jun 27 15:27, Thomas Wolff wrote:
>> Hi,
>> Before a mintty release, I'd like to check Windows console issues with
>> mintty in Windows 10,
>> see https://github.com/mintty/mintty/issues/439
>> As I don't have Windows 10, maybe someone can help out testing;
>> there is some kind of resource magic which I'm not familiar with (and I
>> remember it's been discussed here in some context); there is a file res.mft
>> in mintty with these 2 lines:
>>        <supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}"/> <!-- Vista
>> -->
>>        <supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/> <!-- 7 -->
>> and I have a vague idea that specific lines should be added to facilitate
>> seamless integration with Windows 8, 8.1, and 10.
>> Which lines could that be?
>    $ strings /usr/lib/default-manifest.o
>
> If that's all there is to mintty's manifest, you can remove it and
> just build mintty without explicit manifest.
Well, there is also a res.rc without which mintty loses its Options 
menu. And it does not compile without the res.mft, so I guess it's needed.
> In that case GCC will apply /usr/lib/default-manifest.o to the executable.
>
> Did you see my mail to you from 2015-06-23?
Yes, and I wonder how my response got lost :/
I was remotely aware of that mailing list and had no plan to resurrect 
it (unless you would convince me it's worth it);
I think it's sufficient for this project to have one of issue tracker or 
mailing list/forum, not both. And an issue tracker has the valuable 
advantage that you can close issues...

Thomas

--
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