Mercurial > pidgin

annotate HACKING @ 32174:63e7d226b760

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Re-arrange these doxygen comments. For comments longer than a few words, putting the comment before the variable like this seems cleaner than trying to cram it on the same line as the variable and using lots of crazy indentation. Anyone have a strong opinion either way?
author Mark Doliner <mark@kingant.net>
date Sun, 18 Sep 2011 20:18:33 +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