Re: Blurt code in Github

2015-05-13 Thread Elifarley Callado Coelho Cruz
Where can I see the torture test results ? Maybe it would be good to use Wercker ( which is free - http://wercker.com/ ) to make sure we always have binaries automatically built for every new commit. Elifarley Cruz Professional info: http://linkd.in/elifarley | https://github.com/elifarley |

Re: Blurt code in Github

2015-05-13 Thread Elifarley Callado Coelho Cruz
Using port 80 would be easier for me, any chance of configuring Apache to map that? Maybe I could do that for you. And what is the URL for Tux3's Worcker page ? Thanks! Elifarley Cruz Professional info: http://linkd.in/elifarley | https://github.com/elifarley |

Re: Blurt code in Github

2015-05-13 Thread Daniel Phillips
On 05/13/2015 07:07 AM, Elifarley Callado Coelho Cruz wrote: Where can I see the torture test results ? You mean, http://buildbot.tux3.org:8010/ ? I am not as familiar with it as I should be. Maybe it would be good to use Wercker ( which is free - http://wercker.com/ ) to make sure we

Blurt code in Github

2015-05-12 Thread Elifarley Callado Coelho Cruz
Hi Daniel, I've copied your Blurt code and posted it at https://github.com/*tux3fs* /blurt Also notice that I've created an organization in Github named *tux3fs *(as tux3 was already taken, and tux3fs sounds good to me) to make it easier for people to discover tux3's source code, so maybe you