-
jamessan pushed 1 commit(s) to refs/heads/master in the supybot Git repository of the Supybot project.
2009-12-10 13:09:42 UTC in Supybot
-
jamessan pushed 1 commit(s) to refs/heads/master in the supybot Git repository of the Supybot project.
2009-11-29 02:22:06 UTC in Supybot
-
jamessan pushed 1 commit(s) to refs/heads/master in the supybot Git repository of the Supybot project.
2009-11-28 22:48:33 UTC in Supybot
-
jamessan pushed 1 commit(s) to refs/heads/master in the supybot Git repository of the Supybot project.
2009-11-22 19:32:28 UTC in Supybot
-
Fix in git master branch, commit 07e283f.
2009-11-19 01:12:28 UTC in Supybot
-
jamessan pushed 1 commit(s) to refs/heads/master in the supybot Git repository of the Supybot project.
2009-11-19 01:11:24 UTC in Supybot
-
We accept non-rfc compliant nicks in supybot-wizard likely because we aren't sure whether the server the bot will connect to is enforcing rfc-compliant nicks.
Either we use the current behavior and the bot can't start when using a non-rfc nick and connecting to an enforcing server or we change the behavior and people get an error in the wizard using a nick they know will work on a...
2009-11-19 00:50:41 UTC in Supybot
-
When I first transitioned the repository from svn to git, there was some duplicate history that I didn't notice for a while. I finally got tired of having that around, and removed that from the repo. While I was mucking around, I decided to rename the tags so they start with 'v' (as is common practice) and adjust the emails of people that have made commits to use their users.sourceforge.net...
2009-11-04 08:05:05 UTC in Supybot
-
You didn't have the bot opped. It can't kick if it isn't opped. When it would have kicked someone if it were opped, it says "*BANG* Hey, who put a blank in here?!".
2009-11-01 14:55:20 UTC in Supybot
-
Thanks for the bug. I kept forgetting about this issue. It's been fixed in git commit 98f7c8f by renaming Owner.log to Owner.logmark.
2009-10-31 22:24:56 UTC in Supybot
