X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00,KHOP_PGP_SIGNED,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Date: Thu, 31 May 2012 16:01:43 -0500 From: "Ryan C. Underwood" To: cygwin AT cygwin DOT com Subject: How to "bisect" Cygwin? Message-ID: <20120531210143.GA11744@localhost.localdomain> Reply-To: nemesis AT icequake DOT net MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bp/iNruPH9dso1Pn" Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com --bp/iNruPH9dso1Pn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable How can I "bisect" Cygwin i.e. by setting a certain date at which to install packages that were current as of that date, and checking if problem remains, so as to track down the date a problem/different behavior was introduced sometime in the past year? Actually, if I could start with the Cygwin DLLs themselves, that would probably get me to the bottom of it. --=20 Ryan C. Underwood, --bp/iNruPH9dso1Pn Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iD8DBQFPx9w3IonHnh+67jkRAlBJAKCy/rPQD41QEnT4U1hNCWhQh1ZcPACfYauM Iltfo17aSdRLywB7GcQrhts= =rC+p -----END PGP SIGNATURE----- --bp/iNruPH9dso1Pn--