Pango 1.24.0 is now available from:
http://download.gnome.org/sources/pango/1.24/
d209f41079833cd2ef2c5e580ab9c5ee pango-1.24.0.tar.bz2
eb2394d143012432b73b8633ed632726 pango-1.24.0.tar.gz
This is a stable release providing new functionality as compared to
Pango-1.22, while maintaining sou
On Thu, Mar 12, 2009 at 01:56:05PM +0100, Maik Zumstrull wrote:
> Worked on fifth-or-so attempt, must have been a temporary server glitch.
You likely have a (transparent) proxy with multiple IP addresses. Don't
limit the login to your IP address when logging in.
--
Regards,
Olav
On Mon, Mar 16, 2009 at 5:51 PM, Havoc Pennington
wrote:
> Hi,
>
> On Mon, Mar 16, 2009 at 12:45 PM, IdaRub wrote:
>> After reading the gobject code a bit more, it seems that weak
>> references are fired on dispose, not finalize:
>>
>
> Right, that's correct.
>
>> All of the documentation I could
Hi,
On Mon, Mar 16, 2009 at 12:45 PM, IdaRub wrote:
> After reading the gobject code a bit more, it seems that weak
> references are fired on dispose, not finalize:
>
Right, that's correct.
> All of the documentation I could find states that it happens during
> finalization, but it seems it sho
After reading the gobject code a bit more, it seems that weak
references are fired on dispose, not finalize:
static void
g_object_real_dispose (GObject *object)
{
g_signal_handlers_destroy (object);
g_datalist_id_set_data (&object->qdata, quark_closure_array, NULL);
g_datalist_id_set_data (&
On Fri, 2009-03-13 at 20:57 +0100, Alexander Larsson wrote:
> On Fri, 2009-03-13 at 18:45 +0100, Alexander Larsson wrote:
> > One compromise we could make it to only fsync in the case we're actually
> > overwriting an existing file. This would mean that we don't risk loosing
> > both the old and th
On Mon, 2009-03-16 at 11:55 +0100, Sven Herzberg wrote:
> Am Montag, den 16.03.2009, 11:49 +0100 schrieb Alexander Larsson:
> > On Mon, 2009-03-16 at 10:23 +, Michael Meeks wrote:
> > > On Sun, 2009-03-15 at 10:19 +0100, Alexander Larsson wrote:
> > > > But there are milllions of lines of code
Am Montag, den 16.03.2009, 11:49 +0100 schrieb Alexander Larsson:
> On Mon, 2009-03-16 at 10:23 +, Michael Meeks wrote:
> > On Sun, 2009-03-15 at 10:19 +0100, Alexander Larsson wrote:
> > > But there are milllions of lines of code that does the rename as
> > > atomic replace and the chances th
On Mon, 2009-03-16 at 10:23 +, Michael Meeks wrote:
> On Sun, 2009-03-15 at 10:19 +0100, Alexander Larsson wrote:
> > The debate is far from over with this. gio should be made slower and do
> > unnecessary syncronous I/O in order to fulfill the standards, yes.
>
> Sure, it should fsync o
On Sun, 2009-03-15 at 10:19 +0100, Alexander Larsson wrote:
> The debate is far from over with this. gio should be made slower and do
> unnecessary syncronous I/O in order to fulfill the standards, yes.
Sure, it should fsync on ext4-before-it-was-fixed systems - it sucks to
loose data; th
10 matches
Mail list logo
