On Sun, 14 Nov 2010, Frederic Bouvier wrote:
Hi Gene,
- "Gene Buckle" a écrit :
> Ah, sorry to disappoint, but you have to commit to Git first - unlike
> some setups, we haven't engineered a 'compile before publish' system.
> Hence my ensuring I have time to watch Hudson *after* a commit
On 14 Nov 2010, at 08:19, Frederic Bouvier wrote:
>> What about offering those with commit rights the ability to trigger
>> builds on their own? That way if they break it, they can fix it and re-start
>> the build. I've enabled the "email the person that broke the build"
>> option, but I don't
Hi Gene,
- "Gene Buckle" a écrit :
> > Ah, sorry to disappoint, but you have to commit to Git first - unlike
> > some setups, we haven't engineered a 'compile before publish' system.
> > Hence my ensuring I have time to watch Hudson *after* a commit, and, for
> > example, make a fix commit
On Sat, 13 Nov 2010, James Turner wrote:
>
> On 12 Nov 2010, at 23:44, Curtis Olson wrote:
>
>> My personal rule-of-thumb is to only commit when I've got time to watch the
>> Hudson board go green - it's on an hourly poll at the moment, though we can
>> allow other users to manually kick off bui
On 13 Nov 2010, at 19:36, Tim Moore wrote:
> There's never been a guarantee that the development sources compile for
> everybody at all moments. That's why they are development sources. I
> appreciate the Hudson process and quite often the change to get things
> compiling on a given platform a
There's never been a guarantee that the development sources compile for
everybody at all moments. That's why they are development sources. I
appreciate the Hudson process and quite often the change to get things
compiling on a given platform are obvious, but sometimes they aren't and one
needs to r
On Sat, Nov 13, 2010 at 7:35 AM, Arnt Karlsen wrote:
> On Sat, 13 Nov 2010 09:57:14 +, James wrote in message
>> On 12 Nov 2010, at 23:44, Curtis Olson wrote:
>> > My personal rule-of-thumb is to only commit when I've got time to
>> > watch the Hudson board go green - it's on an hourly poll at
On Sat, 13 Nov 2010 09:57:14 +, James wrote in message
<0275fe52-84ce-4e88-a29c-b1382f3ae...@mac.com>:
>
> On 12 Nov 2010, at 23:44, Curtis Olson wrote:
>
> > My personal rule-of-thumb is to only commit when I've got time to
> > watch the Hudson board go green - it's on an hourly poll at th
On Sat, Nov 13, 2010 at 3:57 AM, James Turner wrote:
>
> On 12 Nov 2010, at 23:44, Curtis Olson wrote:
>
> > My personal rule-of-thumb is to only commit when I've got time to watch
> the Hudson board go green - it's on an hourly poll at the moment, though we
> can allow other users to manually kic
On 12 Nov 2010, at 23:44, Curtis Olson wrote:
> My personal rule-of-thumb is to only commit when I've got time to watch the
> Hudson board go green - it's on an hourly poll at the moment, though we can
> allow other users to manually kick off builds, if you ask Gene nicely.
>
> How do you get
On Fri, Nov 12, 2010 at 5:11 PM, James Turner wrote:
> My personal rule-of-thumb is to only commit when I've got time to watch the
> Hudson board go green - it's on an hourly poll at the moment, though we can
> allow other users to manually kick off builds, if you ask Gene nicely.
>
How do you g
On 12 Nov 2010, at 21:54, Curtis Olson wrote:
> I'm pushing a different fix which follows previous precedence already used in
> the setBlocking() function later in this same source file. Apologize if I
> break things again.
Curt, could you create a flightgear-builds mailing-list, and Gene/mys
I'm pushing a different fix which follows previous precedence already used
in the setBlocking() function later in this same source file. Apologize if
I break things again.
On Fri, Nov 12, 2010 at 2:24 PM, Gene Buckle wrote:
> On Fri, 12 Nov 2010, Frederic Bouvier wrote:
>
> >> > Thanks Fred! We
On Fri, 12 Nov 2010, Frederic Bouvier wrote:
>> > Thanks Fred! We're back to a green board. :D
>
> Would you mind restarting a linux build, just in case ?
>
Will do!
g.
--
Proud owner of F-15C 80-0007
http://www.f15sim.com - The only one of its kind.
http://www.simpits.org/geneb - The Me-109F/
>
> Thanks Fred! We're back to a green board. :D
Would you mind restarting a linux build, just in case ?
-Fred
--
Frédéric Bouvier
http://my.fotolia.com/frfoto/ Photo gallery - album photo
http://www.youtube.com/user/fgfred64 Videos
---
On Fri, 12 Nov 2010, Frederic Bouvier wrote:
- "Gene Buckle" a écrit :
On Fri, 12 Nov 2010, Curtis Olson wrote:
> Are you able to test local changes? What would happen if you
changed line
> #203 of simgear/io/raw_socket.cxx to:
>
>setsockopt( handle, SOL_SOCKET, SO_REUSEADDR,
>
- "Gene Buckle" a écrit :
> On Fri, 12 Nov 2010, Curtis Olson wrote:
>
> > Are you able to test local changes? What would happen if you
> changed line
> > #203 of simgear/io/raw_socket.cxx to:
> >
> >setsockopt( handle, SOL_SOCKET, SO_REUSEADDR,
> >(void *)&opt_boolean,
On Fri, 12 Nov 2010, Curtis Olson wrote:
> Are you able to test local changes? What would happen if you changed line
> #203 of simgear/io/raw_socket.cxx to:
>
>setsockopt( handle, SOL_SOCKET, SO_REUSEADDR,
>(void *)&opt_boolean, sizeof(opt_boolean) );
>
> In other words, inser
On Fri, 12 Nov 2010, Curtis Olson wrote:
> Are you able to test local changes? What would happen if you changed line
> #203 of simgear/io/raw_socket.cxx to:
>
>setsockopt( handle, SOL_SOCKET, SO_REUSEADDR,
>(void *)&opt_boolean, sizeof(opt_boolean) );
>
> In other words, inser
Are you able to test local changes? What would happen if you changed line
#203 of simgear/io/raw_socket.cxx to:
setsockopt( handle, SOL_SOCKET, SO_REUSEADDR,
(void *)&opt_boolean, sizeof(opt_boolean) );
In other words, insert (void *) in front of &opt_boolean
Does that clean
20 matches
Mail list logo
