Blurt code in Github

[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
 | http://openhatch.org/people/elifarley/
Google Plus RSS/Atom Feed: http://bit.ly/elifarley-plusfeed
Bookmarks: http://delicious.com/elifarley
http://twitter.com/elifarley
-

 " Do not believe anything because it is said by an authority, or if it  is
said to come from angels, or from Gods, or from an inspired source.
Believe it only if you have explored it in your own heart and mind and body
and found it to be true.  Work out your own path, through diligence."
- Gautama Buddha

On Wed, May 13, 2015 at 12:39 PM, Daniel Phillips <daniel at phunq.net> wrote:

> 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 always
> > have binaries automatically built for every new commit.
>
> Hirofumi already set that up. By the way, Hirofumi is an amazing sysadmin,
> however he is an even more amazing developer. Sharing some of that load
> would be a win.
>
> Right now, we have an fsync patch set that needs review and torture
> testing before it lands in the public repo, but I am not in any hurry.
> It might possibly make sense to post it to tux3 list, or lkml even,
> so at least people can see its real, or try it if they have the
> interest.
>
> One stupid issue is, ever since Kmail got busted for life, I have no
> email client that I also like to use, that is capable of posting
> patches reliably, without mangling them. I'm using Trojita because
> it can handle lkml, but the composer is hopelessly awful. So I
> compose in Thunderbird, which is also awful but at least usable.
> Not sure what to do about that.
>
> Regards,
>
> Daniel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://phunq.net/pipermail/tux3/attachments/20150513/36aac1e8/attachment-0001.html>