3 Nov
2012
3 Nov
'12
2:30 a.m.
I can definitely understand that! Why don't you
stick with the Oct. 29
build until I figure out what happened. :-)
Sure. My desktop is again stable with the Oct. 29 package set. I save my package sets for
this exact purpose. :)
Somebody has to test GIT on a continual basis or these bugs would remain undiscovered for
long periods. You know me --- I can break, er test, things as fast as you patch them. :)
Some breakage is expected but sometimes the breakage impairs usability. I was almost
tolerating the menu item highlighting breakage but the loss of the sequential Alt key
killed me.
I only get frustrated when we are not informed of these major overhauls and the commit
page doesn't update for several days at a time. We then have no forewarning of
potential breakage or what to test (people using the GIT branch accept that they test
every day). When the commit page is current I can figure out what to reverse to help
debug. When the commit page isn't updated there is no way not to know there are
subsequent commits. At that point trying to reverse anything becomes classic spaghetti.
Well, there probably is a way with a fancy script of some sort to parse each module's
commits, but I don't have anything like that.
I guess the whole point is with a lack of communication the proverbial left hand does not
know what the right hand is doing. :)
Darrell