Re: ben-mule build failure report.

rendhalver> is ben subscribed to the build reports list as well ?? No. Ben has a problem that is not RSI, but has similar effects on his productivity. See his .sig for an URL describing the situation. I monitor build-reports and if there's something that needs Ben's immediate attention, I pass it on. I've told him that people have had problems building on Unix recently, but the branch is in flux (he plans to merge back to mainline early next week), so he just wants to get that done early (spring break so he has time to respond to bug reports). rendhalver> i have been having trouble getting his branch to rendhalver> compile on FreeBSD I believe Ben basically tests on native Windows and Cygwin with all the trimmings. So there are probably issues with "real" Unices that he doesn't catch, but they should be straightforward to fix. rendhalver> would it be useful to have the branch added to the rendhalver> SUCCESS|FAILURE header for the subject ? and maybe the rendhalver> major options like GTK and MULE ? Not really, for my use. I have a (now bitrotted) script to collect option statistics from the header and body. For the headers, success or failure is critical, followed by version then platform. Sticky tag, if any, would be nice. I guess you could grep ./CVS/Entries for version.sh. That gives a sense of the state of the branch. Options and other details are mostly useful if you're trying to find something "close" to a problem build. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Don't ask how you can "do" free software business; ask what your business can "do for" free software.