![](https://secure.gravatar.com/avatar/15f985dc1d6a150767736a0c65e9ef35.jpg?s=120&d=mm&r=g)
Has this been fixed? I have not been pulling from it because I didn't want the FLTK-1.3 code to land on me. Regards, Jeremy Henty
![](https://secure.gravatar.com/avatar/ccd61499c5254c92866127c8014802ef.jpg?s=120&d=mm&r=g)
On Sat, Mar 19, 2011 at 01:11:22PM +0000, Jeremy Henty wrote:
Has this been fixed? I have not been pulling from it because I didn't want the FLTK-1.3 code to land on me.
No not yet. BTW, you can always check with "hg incoming" what you would get on a pull. Cheers, Johannes
![](https://secure.gravatar.com/avatar/15f985dc1d6a150767736a0c65e9ef35.jpg?s=120&d=mm&r=g)
Johannes Hofmann wrote:
On Sat, Mar 19, 2011 at 01:11:22PM +0000, Jeremy Henty wrote:
Has this been fixed? I have not been pulling from it because I didn't want the FLTK-1.3 code to land on me.
No not yet. BTW, you can always check with "hg incoming" what you would get on a pull.
OK, thanks for the tip! I'll keep checking. Jeremy
![](https://secure.gravatar.com/avatar/d74cf44f70f28e6f704786ea10bdb192.jpg?s=120&d=mm&r=g)
On Sat, Mar 19, 2011 at 07:44:26PM +0100, Johannes Hofmann wrote:
On Sat, Mar 19, 2011 at 01:11:22PM +0000, Jeremy Henty wrote:
Has this been fixed? I have not been pulling from it because I didn't want the FLTK-1.3 code to land on me.
No not yet. BTW, you can always check with "hg incoming" what you would get on a pull.
I asked Andreas to fix it again (I messed with it twice) and now it's fixed. Thanks to him. -- Cheers Jorge.-
participants (3)
-
jcid@dillo.org
-
Johannes.Hofmann@gmx.de
-
onepoint@starurchin.org