OK, so current DRI sources have been merged. Sorry for the CVS logs not being clear on the mailing list, but what happened was that after I noticed that the Mesa log was huge I went and turned off logging until after the conflict resolution. Probably should have turned it back on before conflict resolution. On a related note, I feel like CVSROOT modifications should also go to the mailing list, so people can know, "OK, anholt's playing around with big imports and things will have changed." Any opposition to doing so?
Now I'm doing final build testing and looking at hooking development drivers up to the build in an appropriate way. We'll also need someone to take a look at snapshots. One easy thing to do (I hope) would be to just update the current snapshot scripts for the new tree. The other possibility is to integrate snapshots into a DRI tinderbox script, which I think would be pretty nice to have. The advantage of the tinderbox route is that we get a pretty nifty way to look at the logs when the build fails, and better knowledge of just when the build began failing, should development become active enough that nailing breakages down within the day is useful. -- Eric Anholt [EMAIL PROTECTED] http://people.freebsd.org/~anholt/ [EMAIL PROTECTED] ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
