This is the mail archive of the
cygwin-developers@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: old snapshots
- To: cygwin-developers at sourceware dot cygnus dot com
- Subject: Re: old snapshots
- From: Chris Faylor <cgf at cygnus dot com>
- Date: Thu, 25 May 2000 23:25:01 -0400
- References: <20000526024958.16761.qmail@web106.yahoomail.com> <200005260257.WAA32216@envy.delorie.com>
- Reply-To: cygwin-developers at sourceware dot cygnus dot com
On Thu, May 25, 2000 at 10:57:19PM -0400, DJ Delorie wrote:
>[cygwin-developers added because this seemed like a generic question]
>> Just because I'm on a slow connection right now, I'll ask, how is
>> CVS tagged to identify a "snapshot" for Cygwin?
>
>It isn't. Snapshots are done by timestamp. The 20000524 snapshot,
>for example, was as of 23:55 EST on the 24th. You can use something
>like "cvs checkout -D '2000-05-24 23:55' winsup" (although the time
>zones might be off; I'm EST and sourceware is PST) to get that day's
>snapshot. I usually omit the time when searching for when a bug was
>introduced.
>
>The neat part about CVS is that you can switch days pretty easily.
>The cvs command above can be used on an existing area, to make the
>minimum number of changes to go from date A to date B. It's much
>faster than downloading snapshots, provided you're in the mood to keep
>a build area around.
>
>You can even do a binary search of a month to find the bug. It only
>takes 5 updates to narrow it down to a day's changes.
FWIW, I do tag the sources when I make a net release. I don't create
a branch or anything. I just tag all of the sources that went into
the cygwin net release.
cgf