im.pidgin.pidgin: b4fd63bb4dd01f0dff314a75235be5fbbe7b98d0

[Mark Doliner]

On Tue, 18 Dec 2007 08:22:41 -0500, Daniel Atallah wrote
> On Dec 18, 2007 3:45 AM, <markdoliner at pidgin.im> wrote:
> > -----------------------------------------------------------------
> > Revision: b4fd63bb4dd01f0dff314a75235be5fbbe7b98d0
> > Ancestor: fa5978af2779532e133e750eb81967e1f9f6c04d
> > Author: markdoliner at pidgin.im
> > Date: 2007-12-18T08:42:41
> > Branch: im.pidgin.pidgin
> >
> > Modified files:
> >        libpurple/dnsquery.c libpurple/network.c libpurple/util.c
> >        libpurple/util.h
> >
> > ChangeLog:
> >
> > Create a purple_gai_strerror() function similar to g_str_error() which
> > calls gai_strerror() then tries to convert the result into UTF-8.  I
> > believe this fixes #3003
> 
> I guess this means that the next im.pidgin.pidgin release will be 2.4.0.
> 
> If we're going to do this, we should probably propagate im.pidgin.next.minor
> ..
> 
> As a side note, there is already a fix in accounts.c to prevent corruption
> of the accounts.xml from a non-UTF-8 error message (of course, this 
> is better because it'll actually provide the correct message).  So,
>  if we want to just put this in the .next.minor branch, that would 
> be ok too.

That totally didn't occur to me at the time.  But I haven't seen anyone
complain about having the next release be 2.4.0... so I guess everyone is ok
with that?  Thanks Daniel!

-Mark