http://bugs.winehq.org/show_bug.cgi?id=2939
------- Additional Comments From inverseparadox@comcast.net 2005-06-05 23:26 ------- I'd like to do that, and in fact I tried, but for some reason (possibly just some lack in my understanding of CVS) I haven't been able to reliably get any granularity more precise than one day. I looked on the archives of the Wine CVS-log mailing list, and there are only six commits which took place on 2005/04/24; I saw one - to wine/dlls/ddraw/ddraw/user.c (changing from revision 1.23 to 1.24) - which looked like it had a remote chance of being related, but passing timestamps from immediately before and immediately after the timestamp on that CVS commit to cvs update does not reliably produce any changes to my local tree at all.
Specifically, if I run
cvs -z3 update -dPA -D "2005-04-24 12:23"
and then run
cvs -z3 update -dPA -D "2005-04-24 12:24"
the latter command does not report any changes (the timestamp on the revision in question is 2005/04/24 12:23:39 - the minute-level precision wouldn't help, as there are other commits in the intervening seconds).
If someone can figure out and explain to me what I'm doing wrong, I'd be glad to do the rest of the refinement necessary to track down the offending commit precisely. I'll note in passing, however, that the error message I'm getting is not precisely the same as the one reported by Luiz (the string in the concluding parentheses is different), and the game I am running is not the same; it is faintly possible that these are two different bugs.
(As far as having a handle on CVS - I lurk, and occasionally contribute, on the development mailing lists for a couple of other projects; one tends to pick up good bug-reporting habits from observation rather quickly that way. I considered joining some of the Wine mailing lists to report this, but the Bugzilla looks to be a more streamlined way of handling things.)
-
Wine Bugs