diff options
| author | Jelmer Vernooij <jelmer@samba.org> | 2005-12-04 22:55:15 +0100 |
|---|---|---|
| committer | Jelmer Vernooij <jelmer@samba.org> | 2005-12-04 22:55:15 +0100 |
| commit | 019c031a8d77fa8f21792ccf0e07c2dfa058ce5f (patch) | |
| tree | 116b7dc98dc8b4d4805a02f7e5d4ce64c95b9eac /doc/README | |
| parent | 500a1b60d3dd0565d215721e0db7ec7da2dec2e0 (diff) | |
| parent | d636233a518fbe46264230866d4b8ea463f1474e (diff) | |
Merge from Wilmer
Diffstat (limited to 'doc/README')
| -rw-r--r-- | doc/README | 17 |
1 files changed, 11 insertions, 6 deletions
@@ -107,11 +107,10 @@ not daemons). See utils/bitlbeed.c for more information about the program. -Just a little note: We run our public server im.bitlbee.org for a couple of -months now, and so far we haven't experienced this problem yet. The only -BitlBee processes killed because of CPU-time overuse were running for a long -time already, they were usually killed during the MSN login process (which -is quite CPU-time consuming). +Just a little note: Now that we reach version 1.0, this shouldn't be that +much of an issue anymore. However, on a public server, especially if you +also use it for other things, it can't hurt to protect yourself against +possible problems. USAGE @@ -145,6 +144,12 @@ WEBSITE You can find new releases of BitlBee at: http://www.bitlbee.org/ +The bug tracking system: +http://bugs.bitlbee.org/ + +Our version control system is Bazaar-NG. Our repository is at: +http://code.bitlbee.org/ + A NOTE ON ENCRYPTION ==================== @@ -186,5 +191,5 @@ also licensed under the GPL. BitlBee - An IRC to other chat networks gateway <http://www.bitlbee.org/> - Copyright (C) 2002-2004 Wilmer van der Gaast <wilmer@gaast.net> + Copyright (C) 2002-2005 Wilmer van der Gaast <wilmer@gaast.net> and others |