projects / irc.git / blame
| Commit | Line | Data |
|---|---|---|
| 3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
| 2 | <HTML> | |
| 3 | <HEAD> | |
| 4 | <TITLE> [IRCServices Coding] Re: [IRCServices Coding] | |
| 5 | </TITLE> | |
| 6 | <LINK REL="Index" HREF="index.html" > | |
| 7 | <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Re%3A%20%5BIRCServices%20Coding%5D&In-Reply-To=1a2.2b95a48.2a1fbc69%40aol.com"> | |
| 8 | <META NAME="robots" CONTENT="index,nofollow"> | |
| 9 | <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> | |
| 10 | <LINK REL="Previous" HREF="000746.html"> | |
| 11 | <LINK REL="Next" HREF="000744.html"> | |
| 12 | </HEAD> | |
| 13 | <BODY BGCOLOR="#ffffff"> | |
| 14 | <H1>[IRCServices Coding] Re: [IRCServices Coding]</H1> | |
| 15 | <B>RT.Mail at verizon.net</B> | |
| 16 | <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Re%3A%20%5BIRCServices%20Coding%5D&In-Reply-To=1a2.2b95a48.2a1fbc69%40aol.com" | |
| 17 | TITLE="[IRCServices Coding] Re: [IRCServices Coding]">RT.Mail at verizon.net | |
| 18 | </A><BR> | |
| 19 | <I>Fri May 24 10:31:37 PDT 2002</I> | |
| 20 | <P><UL> | |
| 21 | <LI>Previous message: <A HREF="000746.html">[IRCServices Coding] Re: Crontab Script | |
| 22 | </A></li> | |
| 23 | <LI>Next message: <A HREF="000744.html">[IRCServices Coding] Services 5.0 alpha 34 released | |
| 24 | </A></li> | |
| 25 | <LI> <B>Messages sorted by:</B> | |
| 26 | <a href="date.html#747">[ date ]</a> | |
| 27 | <a href="thread.html#747">[ thread ]</a> | |
| 28 | <a href="subject.html#747">[ subject ]</a> | |
| 29 | <a href="author.html#747">[ author ]</a> | |
| 30 | </LI> | |
| 31 | </UL> | |
| 32 | <HR> | |
| 33 | <!--beginarticle--> | |
| 34 | <PRE>I feel that what Andrew has done with allowing services admin to | |
| 35 | modify the channel access list is great. There is no need for an | |
| 36 | override command. Trust me. I have worked with services that allowed | |
| 37 | admins to do anything to the channel that people on the channel | |
| 38 | access list could do. Those were and until the final release of 5.0, | |
| 39 | I think still are the best services I have worked with. Its not that | |
| 40 | easy to make a mistake. And usually its not that hard to correct one | |
| 41 | if you do. Just let Andrew get these services finished and released. | |
| 42 | If you still feel the need for him to add an override command in let | |
| 43 | it be an addition to the next version. Just let him get 5.0 out :P | |
| 44 | ||
| 45 | ||
| 46 | </PRE> | |
| 47 | ||
| 48 | <!--endarticle--> | |
| 49 | <HR> | |
| 50 | <P><UL> | |
| 51 | <!--threads--> | |
| 52 | <LI>Previous message: <A HREF="000746.html">[IRCServices Coding] Re: Crontab Script | |
| 53 | </A></li> | |
| 54 | <LI>Next message: <A HREF="000744.html">[IRCServices Coding] Services 5.0 alpha 34 released | |
| 55 | </A></li> | |
| 56 | <LI> <B>Messages sorted by:</B> | |
| 57 | <a href="date.html#747">[ date ]</a> | |
| 58 | <a href="thread.html#747">[ thread ]</a> | |
| 59 | <a href="subject.html#747">[ subject ]</a> | |
| 60 | <a href="author.html#747">[ author ]</a> | |
| 61 | </LI> | |
| 62 | </UL> | |
| 63 | ||
| 64 | </body></html> |