On 7/11/07, Junio C Hamano <gitster@xxxxxxxxx> wrote:
Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: >> I'll see what I can do. As I'm planning on running git on both FreeBSD >> and DragonFly for the forseeable future, and plan to track git's >> evolution (running stable releases if not more bleeding-edge code), I >> can run the test suite every time I build a new git. > > If you want to, I can help you setting up a nightly cron job to fetch what > is the current "next", run the tests, and report failures by email. Wow. Nightly builds of 'next' on various platforms would actually be quite useful, especially from non Linux and non bash world.
I found and fixed the shell issues. Once I've got a "fix" for tar I'll send a patch. I think the BSD sh has a bug wrt to negating the return code from a pipeline. I'd be happy to do a nightly build on my DragonFly box, and that should catch anything that also doesn't work for FreeBSD. The failure modes were exactly the same - though the DFly box has an additional iconv-related problem (with git-mailinfo) that I still haven't tracked down... Is there a canned script to get me started? One issue is that my server is on dynamic IP, and my lame ISP (the local telco) doesn't give me a proper SMTP relay - they want us to send our mail via HTTP to MSN! Completely lame. So sending mail can be an issue, if the receiver blocks mail from dynamic IPs. - David -- If I have not seen farther, it is because I have stood in the footsteps of giants. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
