im.pidgin.pidgin: 59ab2b78429c94d5d0fc77b1b7892accb524e2a4

[Evan Schoenberg]

On Oct 15, 2007, at 8:18 PM, Sadrul Habib Chowdhury wrote:

>> Modified files:
>>        libpurple/protocols/msn/msn.c libpurple/protocols/msn/user.c
>>        libpurple/status.h
>>
>> ChangeLog:
>>
>> Use a #define for the msn 'currentmedia' status attribute in line  
>> with the PURPLE_TUNE_ attributes used in the xmpp prpl
>>
>
> This has been done (differently) in the .next.minor branch (added in
> revision c18d5cd286ee71c937b596b39c52f826f6ba5dc1) (and there's going
> to be some conflicts when the merge happens).
>
> [snip]

Could we please make a policy of mentioning on devel at pidgin.im  
branches like that?  I didn't know .next.minor existed, and if I had  
randomly done a mtn ls its name wouldn't have told me anything about  
its purpose (next.minor relative to what, exactly? perhaps  it was  
there before and I never noticed it?).

>> #define PURPLE_TUNE_YEAR	"tune_year"
>> -#define PURPLE_TUNE_URL	"tune_url"
>> +#define PURPLE_TUNE_URL		"tune_url"
>> +#define PURPLE_TUNE_FULL	"tune_full"
>>
>
> I believe this bumps the minor? If that's the case, we can just merge
> .next.minor right now.

Perhaps I'm confused, but why does this bump the minor?   
im.pidgin.pidgin is already 2.3.0dev, isn't it?

Cheers,
Evan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pidgin.im/pipermail/devel/attachments/20071015/8a00f134/attachment.html>