DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=GAPnmJ10iRvFFJ3xBG6YNoXpmIqCnGu3u2sHRznRipv7M+G+r3Ft0
	1VPP85UeqQLKV7/SrQ98Wpvcxx76o1kn3DFa9+n6nVYh4mV1Rfv629HhgeUlNzbU
	9vIVPM/2Z6Z+5tAZkj8oFN8qNXXEDyq0szUty+p9Ki/ekdt2b4bmyU=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Sun, 15 Feb 2015 10:30:37 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Very slow Cygwin startup on Windows 7
Message-ID: <20150215093037.GG7225@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <3FEEC3A37A0B0A48AA326075128C32EE4DC9F0E8@xmb-rcd-x01.cisco.com> <87mw4nugdx.fsf@Rainer.invalid> <3FEEC3A37A0B0A48AA326075128C32EE4DC9F137@xmb-rcd-x01.cisco.com> <869208266.20150210030528@yandex.ru> <20150212085431.GA10123@calimero.vinschen.de> <789353699.20150213033430@yandex.ru> <20150213085530.GM7818@calimero.vinschen.de> <3265D3F2-EC0E-4E88-8214-00E91A01E1EC@etr-usa.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="n/aVsWSeQ4JHkrmm"
Content-Disposition: inline
In-Reply-To: <3265D3F2-EC0E-4E88-8214-00E91A01E1EC@etr-usa.com>
User-Agent: Mutt/1.5.23 (2014-03-12)

--n/aVsWSeQ4JHkrmm
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Feb 13 14:32, Warren Young wrote:
> > On Feb 13, 2015, at 1:55 AM, Corinna Vinschen <corinna-cygwin@cygwin.co=
m> wrote:
> >=20
> > It reads nicely.  The paragraph starting with "The 1.7.35 release is
> > expected..." needs a tweak as soon as 1.7.35 goes release, of course,
> > but otherwise it's really neat.
>=20
> It also still has a bug from the original, where I didn=E2=80=99t fix a c=
:\cygwin64 -> c:\cygwin.
>=20
> > Any problem to rework for XML and sending as unified patch against the
> > latest version of the file from CVS?
>=20
> I tried to check out a new copy of the Cygwin CVS tree to do the merge
> myself, but I got a public key denied complaint.  The key I tried to
> use *does* work with the new Git setup.exe repo.  Did the key
> configuration get changed when this piece got sliced off?

Definitely not.  The key configuration in terms of your rights are bound
to your group membership.  The setup tool belonged to group
"cygwin-apps", while cygwin belongs to group "src".  If your key doesn't
work anymore, you might ask on the overseers list if they can help to
find out what the problem is.  From here I really can't tell and I'm
no sourceware admin.


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--n/aVsWSeQ4JHkrmm
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJU4Gc9AAoJEPU2Bp2uRE+gHToP/AmHLQax0bUoI6tk6S0IONmZ
Dt7iCroby2P1Smn8gBxEb0BlotA/REFEkZP82/tuLgFsq7PN8KdQaXV+9U9Eeeps
HFjEt3QIh5XtRWXinqXP7fM1LSOiEzAu3Un0LKtX45pRbnilgf7p8p1EkqwBLIsj
dcOiRCJSnGr3ToU4y766Hp4cqCeVGOAXw4KXYzhV9VOwt8NZ3vzTK8s0EmSUjrxO
tZu+2gbPUXtpchqlvIX3wwbqKDcAJEZM8WP+mpKry0CI/JZCH8OS7s/79cLORDUb
0D8ocVhQLAswEKm2YH22PlZim/YLeu6us524gCDyKalMr1npIkF6qAocJ0srh7XX
Yburgs5Z8JFFMvJPhj+U7cAWyWzXBS3ys37w0SJEVwaNXAu3Foi1IrhCQ+GiYgXl
i49KdoFvx+JLx17vqo/HqzotcaV6azCc1vp4JiMFtF1YLDuqbC9N6DxAcTinQ/bY
AC960vDPk5Zc+9AW+CC3yOV0o3FBqWirzK1WJbwpS14odoAJ6frnk4+eUXv1gKgO
DeFObSUZmHYwik8/Lo2UptNlcxSjmkZmFs4Vnz1ydPJVgGDp+uTmZCT/2ryjWiqa
U4za27sk9v5vSUUDxBfF/wsKAUAw580b+iTGI4eDrg4E8dijdz4g3xI4k+ee8Hj2
v19XHXIhnkeEj7DCBMG7
=wGsE
-----END PGP SIGNATURE-----

--n/aVsWSeQ4JHkrmm--