[IRC-Dev CVS] [CVS] Module ircd-ircdev: Change committed

[Toni G. <zo...@us...>]

CVSROOT    : /cvsroot/irc-dev
Module     : ircd-ircdev
Commit time: 2005-01-05 16:38:22 UTC

Modified files:
     doc/en/api/events.txt doc/en/api/features.txt
     doc/en/api/gline.txt doc/en/api/ircd_snprintf.txt
     doc/en/api/joinbuf.txt doc/en/api/jupe.txt doc/en/api/modebuf.txt
     doc/en/api/motd.txt doc/en/api/msgq.txt doc/en/api/privileges.txt
     doc/en/api/send.txt

Log message:

Documentación API en inglés

---------------------- diff included ----------------------
Index: ircd-ircdev/doc/en/api/events.txt
diff -u ircd-ircdev/doc/en/api/events.txt:1.1 ircd-ircdev/doc/en/api/events.txt:1.2
--- ircd-ircdev/doc/en/api/events.txt:1.1	Wed Jan  5 08:32:43 2005
+++ ircd-ircdev/doc/en/api/events.txt	Wed Jan  5 08:38:12 2005
@@ -1,3 +1,5 @@
+$Id: events.txt,v 1.2 2005/01/05 16:38:12 zolty Exp $
+
 The IRC server is built around an event loop.  Until the u2.10.11
 release, this event loop has been rather ad-hoc; timed events are
 hard-coded in, signals are handled inside the signal handler, etc.
Index: ircd-ircdev/doc/en/api/features.txt
diff -u ircd-ircdev/doc/en/api/features.txt:1.1 ircd-ircdev/doc/en/api/features.txt:1.2
--- ircd-ircdev/doc/en/api/features.txt:1.1	Wed Jan  5 08:32:43 2005
+++ ircd-ircdev/doc/en/api/features.txt	Wed Jan  5 08:38:12 2005
@@ -1,3 +1,5 @@
+$Id: features.txt,v 1.2 2005/01/05 16:38:12 zolty Exp $
+
 As of u2.10.11, most of the compile-time configuration options present
 in previous versions of ircu have been provided via the configuration
 file as "features."  This document is intended not only to give an
Index: ircd-ircdev/doc/en/api/gline.txt
diff -u ircd-ircdev/doc/en/api/gline.txt:1.1 ircd-ircdev/doc/en/api/gline.txt:1.2
--- ircd-ircdev/doc/en/api/gline.txt:1.1	Wed Jan  5 08:32:43 2005
+++ ircd-ircdev/doc/en/api/gline.txt	Wed Jan  5 08:38:12 2005
@@ -1,3 +1,5 @@
+$Id: gline.txt,v 1.2 2005/01/05 16:38:12 zolty Exp $
+
 Some users can be very annoying, as any IRC operator can attest.  Some
 can in fact be downright abusive.  Sometimes the best way of dealing
 with these users is to ban them from the entire network.  The G-line
Index: ircd-ircdev/doc/en/api/ircd_snprintf.txt
diff -u ircd-ircdev/doc/en/api/ircd_snprintf.txt:1.1 ircd-ircdev/doc/en/api/ircd_snprintf.txt:1.2
--- ircd-ircdev/doc/en/api/ircd_snprintf.txt:1.1	Wed Jan  5 08:32:43 2005
+++ ircd-ircdev/doc/en/api/ircd_snprintf.txt	Wed Jan  5 08:38:12 2005
@@ -1,3 +1,5 @@
+$Id: ircd_snprintf.txt,v 1.2 2005/01/05 16:38:12 zolty Exp $
+
 These functions are intended to be a complete replacement for sprintf
 and sprintf_irc.  They are a (nearly) complete reimplementation, and
 of course they're snprintf clones, making it more difficult for
Index: ircd-ircdev/doc/en/api/joinbuf.txt
diff -u ircd-ircdev/doc/en/api/joinbuf.txt:1.1 ircd-ircdev/doc/en/api/joinbuf.txt:1.2
--- ircd-ircdev/doc/en/api/joinbuf.txt:1.1	Wed Jan  5 08:32:43 2005
+++ ircd-ircdev/doc/en/api/joinbuf.txt	Wed Jan  5 08:38:12 2005
@@ -1,3 +1,5 @@
+$Id: joinbuf.txt,v 1.2 2005/01/05 16:38:12 zolty Exp $
+
 IRC wouldn't be of much interest without the ability for users to join
 channels.  Of course, they must also be able to leave those channels
 when they get bored of the conversation there.  Users can join or
Index: ircd-ircdev/doc/en/api/jupe.txt
diff -u ircd-ircdev/doc/en/api/jupe.txt:1.1 ircd-ircdev/doc/en/api/jupe.txt:1.2
--- ircd-ircdev/doc/en/api/jupe.txt:1.1	Wed Jan  5 08:32:43 2005
+++ ircd-ircdev/doc/en/api/jupe.txt	Wed Jan  5 08:38:12 2005
@@ -1,3 +1,5 @@
+$Id: jupe.txt,v 1.2 2005/01/05 16:38:12 zolty Exp $
+
 Occasionally, a server will become incorrectly configured or will
 start behaving incorrectly.  Even more rarely, a server will be
 compromised, and a modified version of the server put in place to
Index: ircd-ircdev/doc/en/api/modebuf.txt
diff -u ircd-ircdev/doc/en/api/modebuf.txt:1.1 ircd-ircdev/doc/en/api/modebuf.txt:1.2
--- ircd-ircdev/doc/en/api/modebuf.txt:1.1	Wed Jan  5 08:32:43 2005
+++ ircd-ircdev/doc/en/api/modebuf.txt	Wed Jan  5 08:38:12 2005
@@ -1,3 +1,5 @@
+$Id: modebuf.txt,v 1.2 2005/01/05 16:38:12 zolty Exp $
+
 Generating and parsing channel mode strings is often a very
 complicated process.  The ModeBuf interface, along with the associated
 mode parsing functions, attempt to make this much more programmatic.
Index: ircd-ircdev/doc/en/api/motd.txt
diff -u ircd-ircdev/doc/en/api/motd.txt:1.1 ircd-ircdev/doc/en/api/motd.txt:1.2
--- ircd-ircdev/doc/en/api/motd.txt:1.1	Wed Jan  5 08:32:43 2005
+++ ircd-ircdev/doc/en/api/motd.txt	Wed Jan  5 08:38:12 2005
@@ -1,3 +1,5 @@
+$Id: motd.txt,v 1.2 2005/01/05 16:38:12 zolty Exp $
+
 The server has a Message of the Day (MOTD) which is often used for
 describing the Acceptable Usage Policy, where to get help if you have
 problems, and so on.  Older versions of ircd had a lot of duplicated
Index: ircd-ircdev/doc/en/api/msgq.txt
diff -u ircd-ircdev/doc/en/api/msgq.txt:1.1 ircd-ircdev/doc/en/api/msgq.txt:1.2
--- ircd-ircdev/doc/en/api/msgq.txt:1.1	Wed Jan  5 08:32:43 2005
+++ ircd-ircdev/doc/en/api/msgq.txt	Wed Jan  5 08:38:12 2005
@@ -1,3 +1,4 @@
+$Id: msgq.txt,v 1.2 2005/01/05 16:38:12 zolty Exp $
 Many messages generated by an IRC server are sent to multiple
 recipients.  Previous versions of ircd used DBuf to store these
 messages until they could actually be sent.  The problem with using a
Index: ircd-ircdev/doc/en/api/privileges.txt
diff -u ircd-ircdev/doc/en/api/privileges.txt:1.1 ircd-ircdev/doc/en/api/privileges.txt:1.2
--- ircd-ircdev/doc/en/api/privileges.txt:1.1	Wed Jan  5 08:32:43 2005
+++ ircd-ircdev/doc/en/api/privileges.txt	Wed Jan  5 08:38:12 2005
@@ -1,3 +1,5 @@
+$Id: privileges.txt,v 1.2 2005/01/05 16:38:12 zolty Exp $
+
 Access control becomes more of a problem as you have more and more
 users that need to access certain features.  As it stands, ircu has
 only 3 access levels: ordinary user, local operator, and global
Index: ircd-ircdev/doc/en/api/send.txt
diff -u ircd-ircdev/doc/en/api/send.txt:1.1 ircd-ircdev/doc/en/api/send.txt:1.2
--- ircd-ircdev/doc/en/api/send.txt:1.1	Wed Jan  5 08:32:43 2005
+++ ircd-ircdev/doc/en/api/send.txt	Wed Jan  5 08:38:12 2005
@@ -1,3 +1,5 @@
+$Id: send.txt,v 1.2 2005/01/05 16:38:12 zolty Exp $
+
 The send functions are perhaps the most important API in all of ircd;
 without them, communications would not be possible.  Most of these
 functions are pretty much stand-alone, although one or two are
----------------------- End of diff -----------------------