Mercurial > pidgin
view README.MTN @ 20273:187fa336c1b0
Plucked mysapce tag parsing fixes
applied changes from c5468fb873563f4e1249323a03f5531e192965f3
through 34d642b12b7215d55fd032cd513a7e225715f19a
applied changes from 43e06ba1c67cc326d2d93f14d67709b2375da88b
through bf8de57ed4c36f188044ea0684c201d0a1a67169
applied changes from 854642c5c0ea1bb31de3fd0dc5b0c480b70fc327
through 5a661e7759c94109af265616312c40858ae77e27
author | Evan Schoenberg <evan.s@dreskin.net> |
---|---|
date | Fri, 28 Sep 2007 21:30:15 +0000 |
parents | 83ec0b408926 |
children | e0bcb8cfda74 |
line wrap: on
line source
If you plan to use Pidgin, Finch and libpurple from our Monotone repository, PLEASE read this message in its entirety! Pidgin, Finch, and libpurple are a fast-moving project with a somewhat regular release schedule. Due to the rate of development, the code in our Monotone repository undergoes frequent bursts of massive changes, often leaving behind brokenness and partial functionality while the responsible developers rewrite some portion of code or seek to add new features. What this all boils down to is that the code in our Monotone repository _WILL_ sometimes be broken. Because of this, we ask that users who are not interested in personally tracking down bugs and fixing them (without a lot of assistance from the developers!) use only released versions. Since releases will be made often, this should not prevent anyone from using the newest, shiniest features -- but it will prevent users from having to deal with ugly development bugs that we already know about but haven't gotten around to fixing. If you are interested in hacking on Pidgin, Finch, and/or libpurple, please check out the information available at: http://developer.pidgin.im By far the best documentation, however, is the documented code. If you have doxygen, you can run "make docs" in the toplevel directory to generate pretty documentation. Otherwise (or even if you do!), the header files for each subsystem contain documentation for the functions they contain. For instance, conversation.h contains documentation for the entire purple_conversation_* API, and account.h contains documentation for the purple_account_* API. If you have questions, please feel free to contact the Pidgin, Finch, and libpurple developers by e-mail at devel@pidgin.im or on IRC at irc.freenode.net in #pidgin. Please do as much homework as you can before contacting us; the more you know about your question, the faster and more effectively we can help! Patches should be posted as Trac tickets at: http://developer.pidgin.im