propagate next.minor to i.p.p?

Ka-Hing Cheung khc at hxbc.us
Sun Nov 4 01:07:24 EDT 2007


I have this xmlnode change (attached, deals with preserving node name
and attribute prefixes) that would require a minor bump, which is
required for msnp14 to behave correctly. MSNP14 is already in i.p.p, so
that would require us to bump the minor whenever we release a version
off of i.p.p. If there's no objection, I will propagate next.minor to
i.p.p some time tomorrow.

-khc

-------------- next part --------------
A non-text attachment was scrubbed...
Name: xmlns.diff
Type: text/x-patch
Size: 7472 bytes
Desc: not available
URL: <http://pidgin.im/pipermail/devel/attachments/20071103/d045f00a/attachment-0002.bin>


More information about the Devel mailing list