Mercurial > pidgin.yaz

annotate HACKING @ 28822:9e8d0537d37d

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
I don't think the comment made sense, this is probably what it meant to be. It's only checking status type but not the status message, so it can match the "wrong" status if you have substatuses of different messages. I am not sure if that's a feature or bug though. Seems like a bug to me because it prevents you from setting certain messages if you already have similar transient status. Oh, and why does this matching only work on transient statuses anyway.
author Ka-Hing Cheung <khc@hxbc.us>
date Mon, 26 Oct 2009 06:53:35 +0000
parents d73ee2690376
children
Ignore whitespace changes - Everywhere: Within whitespace: At end of lines:
rev   line source
16174
c95641c98e47 Let's just have HACKING point to Trac, okay?
Richard Laager <rlaager@wiktel.com>
parents:
diff changeset
1 For information on hacking on Pidgin, Finch, or libpurple, see:
c95641c98e47 Let's just have HACKING point to Trac, okay?
Richard Laager <rlaager@wiktel.com>
parents:
diff changeset
2 http://developer.pidgin.im