Well. I didn't expect this.
I ran git with 0.9.15 as good and 0.9.16 as bad. I then did a bisect and compiled the split in a separate directory. It ran O.K. The result of the next split was:
38b43cae82e288557d7119e988d1d22f9799d553 was both good and bad.
It surprised me that it was O.K., because my previous tests indicated that it was not much higher than the 0.9.15 release, and the Wiki indicated that the first split would be in the middle.
I must confess that I can't find my way around the tree, even with qgit. According to qgit, my lower limit is Release 991212 and my Master Origin is a patch by Clinton Simposon on riched20 dated 23/08/06 (Aug 23 2006).
Doug.
On Thu, 24 Aug 2006 02:10 pm, Vijay Kiran Kamuju wrote:
well check this link out http://wiki.winehq.org/GitWine, in it Section 6 raise a bug in Bugzilla, http://bugzilla.winehq.org and also discuss any usage issues in wine-users@winehq.org
Thanks, VJ
On 8/23/06, Doug Laidlaw laidlaws@hotkey.net.au wrote:
I may be on the wrong list.
A program I use has shown a backward step in graphics between Wine 0.9.15 and 0.9.16, and I am trying to find the change responsible. I currently have Wine set as at 2006-06-21 16:21:20 CDT, it is identifying as 0.9.16, and the fault is present. The Web site says to get the CVS history from the mailing list archives, but the archive is only up to mid-2005.
What is the best way to step backwards?
Doug.
When we want to read of the deeds that are done for love, whither do we turn? To the murder column.
- G.B. Shaw.