[cvslog] Module eggdrop1.6: Change committed

cvslog cvs at tsss.org
Sat Dec 29 15:47:01 CST 2001


CVSROOT    : /usr/local/cvsroot
Module     : eggdrop1.6
Commit time: 2001-12-29 21:46:39 UTC
Commited by: Jeff Fisher <guppy at techmonkeys.org>

Modified files:
     doc/BOTNET doc/UPDATES1.6 src/patch.h

Added files:
     doc/first_script.txt

Log message:

added Wcc's patch to update some more docs

---------------------- diff included ----------------------
Index: eggdrop1.6/doc/BOTNET
diff -u eggdrop1.6/doc/BOTNET:1.8 eggdrop1.6/doc/BOTNET:1.9
--- eggdrop1.6/doc/BOTNET:1.8	Tue Nov  6 23:12:01 2001
+++ eggdrop1.6/doc/BOTNET	Sat Dec 29 15:46:29 2001
@@ -1,16 +1,15 @@
-BOTNET SHARING and LINKING v2.0                                   03 Jun 1999
+BOTNET SHARING AND LINKING v2.1                                   29 Dec 2000
 
 
 
 INDEX
 
-I       ABOUT THIS DOCUMENT
-II      TERMS USED
-III     WHAT IS A BOTNET FOR?
-IV      ADDING AND LINKING BOTS
-V       USING BOTFLAGS
-VI      MAKE TWO BOTS SHARE USER RECORD
-
+I.   ABOUT THIS DOCUMENT
+II.  TERMS USED
+III. WHAT IS A BOTNET?
+IV.  ADDING AND LINKING BOTS
+V.   USING BOTFLAGS
+VI.  MAKING BOTS SHARE USER RECORDS
 
 
 
@@ -18,335 +17,237 @@
 
 I. ABOUT THIS DOCUMENT
 
-The purpose of this document is to show you what a botnet is for and why
-it could be useful for you. It also covers botflags and some sharing
-information which you may need for making your bots faster and more reliable.
-
-
+  The purpose of this document is to show you what a botnet is and how
+  it could be useful to you. It also covers botflags userfile sharing.
 
 
 II. TERMS USED
 
-The following are some common terms used in this document.
-If applicable, there is also the associated command named.
-
-
- Botnet
-  The term used to describe multiple bots connected together.
-
-
- Link
-  The term that means the actual linking of one bot
-
-  commands: ".link <botname>" ".unlink <botname>"
-
+  The following are some common terms used in this document:
 
- Hub
-  A bot is described as a hub-bot, if one or more bots are linked to
-  it.
 
+    Botnet
+      A botnet consists of one or more bots connected together.
 
- Leaf
-  A leaf is a non-hub bot connecting to another bot. A leaf has only
-  one other bot connected to it, its hub.  Leaf bots can be assigned
-  the "l" botattr flag to prevent other bots from linking to them.
 
+    Link
+      The term that means the actual linking of a bot
 
- Link Bot
-  A link bot is a bot that is linked to another.  It may or may not be
-  a hubbot, with other bots linked to it besides its hub.
 
+    Hub
+      A bot is described as a hub-bot if one or more bots are linked to
+      it.
 
- Share
-  The term used to describe two bots sharing user records.
 
+    Leaf
+      A leaf is a non-hub bot connecting to a hub-bot. A leaf has only
+      one other bot connected to it, its hub. Leaf bots can be assigned
+      the "l" botattr flag to prevent other bots from linking to them.
 
- Share Bots
-  Share bots is a term used to describe two or more bots sharing user
-  records.
 
+    Link Bot
+      A link-bot is a bot that is linked to another bot. It may or may not 
+      be a hub-bot.
 
- Aggressive Share
-  Term used to describe the direction of sharing user-files.
-  Aggressive share bots will SEND userfiles to another passive bot.
 
+    Share
+      Share is the term used to describe the sharing of user records.
 
- Passive Share
-  Term used to describe the direction of sharing user-files.
-  Passive share bots will accept userfiles from an active/aggressive bot.
 
+    Share Bots
+      A share-bot is a bot which shares user records with one or more 
+      linked bots.
 
-Note:  With eggdrop1.3.x and up, active/passive designations are relative, not
-absolute like the prior versions of eggdrop bots, like 1.1.5. A 1.3+ bot may
-be both active and passive at the same time, in relation to other bots it is
-connected to.
 
-example bottree:
+    Aggressive Share
+      Aggressive share is a term used to describe the direction of sharing 
+      user-files. Aggressive share bots will SEND userfiles to another passive 
+      bot.
 
-superbot
-    |
-    \+intermed
-         |
-         \+peonbot
 
-intermed has a master sharebot, superbot and a slave sharebot, peonbot.
-intermed is passive with [receives from] superbot while being aggressive
-with [sends to] peonbot at the same time.
+    Passive Share
+      Passive share is a term used to describe the direction of sharing 
+      user-files. Passive share bots will accept userfiles from an aggressive
+      share bot.
 
+      Example bottree:
 
- Flags
-  Flags are attributes that determine what a bot can or is allowed to do.
-  Flags can be either global (+s) or channel specific (|+s #lamest).
-  Botnet affecting flags are:
+        BotA
+          |-+BotB
+            `-+BotC
 
-  s   share (Aggressively SEND userfile to a passive bot (assigned +s flag))
-  p   share (Passively ACCEPT userfile from an aggressive bot (assigned +p flag))
-  g   global share (share all channels (this works correctly in 1.4+))
-  h   hub (bot is auto-linked)
-  a   alternate (bot is auto-linked if the hub bot can't be linked)
-  l   leaf (bot is not allowed to link in other bots)
-  r   reject (bot will not be allowed on the net)
-  i   isolate (isolate the party line across a bot link)
-  0-9 user (user defined flags)
+        BotB is linked to a master sharebot, BotA, and a slave sharebot, BotC. 
+	BotB shares passively with [receives from] BotA and shares aggressive 
+	with [sends to] BotC.
 
-  command: ".botattr <botname> [(.+<flag> [#channel]) or (.-<flag> [#channel])]"
 
+    Bot Flags
+      Flags are attributes that determine what a bot can or is allowed to do.
+      Flags can be either global (such as +s) or channel specific (such as 
+      |+s #lamest). See '.help botattr' for help with setting these flags.
+    
+      The following is a list of valid bot flags:
+  
+        s   share aggressively (SEND userfile to a passive bot)
+        p   share passively (ACCEPT userfile from an aggressive bot)
+        g   global share (share all channels)
+        h   hub (automatically link to this bot)
+        a   alternate (automatically link to this bot if the hub bot can't be 
+	    linked)
+        l   leaf (bot is not allowed to link in other bots)
+        r   reject (bot will not be allowed to link)
+        i   isolate (isolate the party line across a bot link)
+        0-9 user defined flags
 
- Address
-  The physical address, containing the host and port address of the bot.
-  i.e. lame.org:3333
 
-  command: ".chaddr <botname> <hostaddress:botport[/userport]>"
 
+    Address
+      The physical address, containing the address and port of the bot.
+      For example: lame.org:3333. You can change a bot's address with
+      ".chaddr <botname> <hostaddress:botport[/userport]>".
 
- Relay
-  The relay port number of the bot is defined in the config file.
- Note that you can define one port for telnet connections to other bots
- and another for relay connections.
 
+    Relay
+      The relay port number of the bot is defined in the config file.
+      Note that you can define one port for bots and another for user 
+      connections. You can use ".relay <botname>" to relay to another 
+      bot.
 
- Relay connection
- A relay connection is used to relay (jump) to another bot in DCC chat.
- You can still relay to  another bot even if this is not defined in the
- conf file.
 
- command: ".relay <botname>"
+    Relay Connection
+      A relay connection is used to relay (jump) to another bot via telnet
+      or DCC chat. You can relay to another bot even if the remote bot is
+      not linked. You can use ".relay <botname>" to relay to another bot.
 
 
- Port
-  The telnet port is used by the bot to communicate with other bots and/or
-  users. Note that you can define two separate ports for user and bot
-  connections.
+    Port
+      The telnet port is used by the bot to communicate with other bots 
+      and/or users. Note that you can define separate ports for user and bot
+      connections.
 
 
 
 
-III. WHAT IS A BOTNET FOR?
-
-Basically a botnet is useful if you want to use more then one bot to protect
-your channel.  Bots linked a botnet can perform script controlled tasks.
-Such a script can be get-ops (ops each bot in a botnet) or some kind of a
-prevent-flood stuff. Just take a look at the script directories on
-ftp://ftp.eggheads.org and you'll find a lot of botnet scripts.
-
-Also, linked bots can share common user records (global or channel specific)
-between each other which helps reduce the time needed to maintain a
-complete, up to date user record database, needed if you operate your
-channels in a +bitch mode. However, a warning - such sharing, with current
-designs, may allow a user on one bot, even a slave bot to alter, change or
-manipulate the entire botnet userfiles and use the botnet to take control of
-your channel away from you.
-
+III. WHAT IS A BOTNET?
 
+  A botnet consists of one or more bots linked together. This can allow bots
+  to op each other securely, control floods efficiently, and share user lists, 
+  ban lists, exempt/invite lists, and ignore lists (if sharing is enabled).
 
 
 IV. ADDING AND LINKING BOTS
 
-With the common terms out of the way we can start with the process of
-linking two bots. Before you start you have to know the following:
-
-        -  What are the domains and ports of the bots.
-
-Let's say there is BotA on lame.org listening to port 3333 and BotB
-on irc.org listening to port 4444. Now you have to add each Bot to the
-other's userfile (including hostmask, address and listening port of the
-other bot). In BotA's console you have to type ".+bot BotB irc.org:4444"
-(assuming that BotB is in the channel and so the hostmask is grabbed
-automatically, otherwise you have to add it manually with ".+host") and on
-BotB's console ".+bot BotA lame.org:3333".
-At this point you can link them for the first time manually by typing
-".link BotA" in BotB's console (or in reverse, of course with BotB ".link BotB"
-in BotA's console). The bots will now give themselves randomized passwords,
-which are *not* stored encrypted in the userfile. Now you've generated your
-first botnet.
-Note that you can add and link as many Bots as you want to your botnet.
-
-
-
+  With the common terms out of the way, we can start with the process of
+  linking two bots. Before you start, you need to know the address and
+  port of each bot you wish to link.
 
-V       USING BOTFLAGS
+  Here is an example senario:
+  
+    BotA is on lame.org listening on port 3333, and BotB is on irc.org 
+    listening on port 4444. First, you have to add each Bot to the other's 
+    userfile. On BotA, you would type '.+bot BotB irc.org:4444'. If BotB is 
+    on a common channel with BotA, BotB's hostmask is automatically added.
+    Otherwise, you have to add the hostmask manually with the '.+host'
+    command. On BotB, you would type '.+bot BotA lame.org:3333'.
 
-Botflags are needed to assign special functions and tasks to your bots.
+    At this point, you can link the two bots by typing '.link BotA' on BotB (or 
+    '.link BotB' on BotA). The bots will now give themselves random passwords
+    which are *not* stored encrypted in the userfile. Note that you can link as 
+    many bots as you wish to your botnet.
 
- "h" (hub)
-  If you want your bots to auto-link after getting unlinked or started (due
-  to a crash or a server reboot), you have to assign the botattr +h to the
-  bot you want the bot to link to.
-  Note, if you set multiple bots +h, the bot only attempts to link to one.
 
-  command: ".botattr <botname> +h"
 
 
- "a" (alternate)
-  If your bots are for some reason not able to link to their hub, they will
-  attempt to connect to an other "alternate-hub", which you can define by
-  setting "+a" on one bot.
-  Note, you can assign +a only to one bot at a time!
+V. USING BOTFLAGS
 
-  command: ".botattr <botname> +a"
+  Botflags are needed to assign special functions and tasks to your bots.
+  Bot flags are set with the '.botattr' command. See '.help botattr' for
+  help with this command. The following is a list of botflags and their 
+  functions:
 
+    "h" (hub)
+      If you want your bot(s) to automatically link/relink, you can assign 
+      the +h botflag each bot's hub. Note that if you set multiple bots +h, 
+      the bot only attempts to link to one.
 
- "l" flag (leaf)
-  This flag assigned to a link bot will cause your bot to unlink the leaf
-  one, if it allows any other bots to link to it.
 
-  command: ".botattr <botname> +l"
+    "a" (alternate)
+      If your bots are, for some reason, unable to link to their hub, they 
+      will attempt to connect to an alternate hub. You can assign a bot as
+      an alternate hub by giving it the +a botflag.
 
 
- "r" flag (reject)
-  If you assign this flag to a bot, it won't be tolerated on your botnet and
-  will be unlinked, if it tries to link to your bot or any other bot.
+    "l" (leaf)
+      This flag, assigned to a link bot, will prevent the link bot from linking
+      other bots to your botnet.
 
-  command: ".botattr <botname> +r"
 
+    "r" (reject)
+      If you assign this flag to a link bot, the link bot will not be allowed
+      to link to the botnet.
 
- "i" flag (isolate)
-  Setting this flag to a bot will isolate the partyline between your bot(net)
-  and the other bot(net).
 
-  command: ".botattr <botname> +i"
+    "i" (isolate)
+      This flag isolates a link bot's partyline from the rest of the botnet.
+      Anything said on the link bot's partyline won't appear on the rest of 
+      the botnet.
 
 
- "0-9" flag (user)
-  These 10 flags aren't hard-coded into eggdrop and can be assigned by scripts
-  or just for fun :-)
+    "s" (SEND userfile to)
+      +s   Giving a link bot this flag will make the bot share aggressively 
+           with the link bot. See 'Aggressive Share' in section II of this 
+	   document for more information on aggressive sharing.
 
-  command: ".botattr <botname> +(0-9)"
+      |s     +s bots need this flag for each channel you want to share.
 
 
- "s" flag (SEND userfile to bots assigned the +s flag)
-   +s   If you set on BotA's console BotB +s then BotA will try to send his
-        userfile (parts selected by |s and g flags) aggressively to BotB.
+    "p" (ACCEPT userfile from)
+      Giving a link bot this flag will make the bot share passively 
+      with the link bot. See 'Passive Share' in section II of this 
+      document for more information on passive sharing.
 
-        command: ".botattr <botname> +s"
 
-   |s   With this flag you can define channels, which you want your bots
-        to share.
-        Note that you can use this flag only on +s bots!
+    "g" (global share)
+      This flag allows the sharing of all channels with a link bot.
 
-        command: ".botattr <botname> |s #lamest"
 
- "p" flag (ACCEPT userfile FROM bots assigned the +p flag)
-  If you assign this flag to another bot, your bot will accept userfiles
-  sent from the aggressive bot (as much as you've allowed with |+s or +g)
+    "0-9" (user-defined)
+      These 10 flags are user-defined can be used by scripters.
 
-        command: ".botattr <botname> +p"
 
 
- "g" flag (global share)
-  If you set this flag on your +s or +p bot, |s and |+s are getting obsolete.
-  Every ban and every user on every single channel will be transferred/accepted.
+VI. MAKING BOTS SHARE USER RECORDS
 
-        command: ".botattr <botname> +g"
+  Before you start preparing your bots for sharing, make sure that
+  you've loaded the transfer and share modules. You also have to ensure 
+  that each channel you wish to share is set +shared (see '.help chanset'
+  and '.help chaninfo').
 
+  By using specific botflags, you can cause your bot to share aggressively
+  with some link bots, and passively with others. For sharing to work, flags
+  must be set properly on both the passive and the aggressive bots. An aggressive 
+  bot will not share userfiles with another aggressive bot; a passive bot will 
+  not share userfiles with another passive bot.
 
+  A bot will send userfiles to any bots with the +s botflag.
 
+  A bot will accept userfiles from any bot with the +p botflag.
 
-VI      MAKE TWO BOTS SHARE USER RECORDS
+  Giving BotB the +s botflag on BotA will not make BotB accept BotA's userfile. 
+  It will only make BotA attempt to send its userfile to BotB.
 
-Before you start preparing your bots for sharing, you have to make sure that
-you've loaded the transfer, share and filesys module into your bot (look
-through the conf). You also have to ensure that the channel, which user records
-should be shared, is set +shared.
+  Giving BotA the +p botflag on BotB will not make BotA send its userfile
+  to BotB. It will only give BotA permission to send BotB a userfile.
 
-When you are adding bot attribute flags to yourbot for other bots to be
-linked, so that they will all share a common userfile, you cannot dictate
-how the other link bots will react by setting botattr flag for them in
-yourbot.  You can only control how you want yourbot to react to those bots
-when they link.
+  If the flags on both bots do not create a +s+p pair, the bots will link but
+  will not share. If the +s+p pair is set properly, but the userfile transfer
+  fails for some reason, the bots will unlink.
 
-By setting specific botattr flags, you can cause your bot to be aggressive
-with some link bots and to be passive with other link bots.
-
-But remember, no botattr settings in yourbot have any control over how the
-other bots will react with yourbot.
-
-For sharing to work, the flags must be coordinated with one bot agreeing to
-be passive and accept and the other link bot agreeing to send or share it's
-userfile.  No setting in yourbot can force another bot to accept files
-yourbot tries to send nor can any such flag force another bot to send or
-share it userfile.  It has to be by mutual agreement to work.  Each bot has
-total control of it own userfile sending and receiving functions.
-
-Two primary botattr flags establish the pecking order, +s and +p, defining
-which bot, by mutual agreement, is to be the aggressive/active bot that
-sends the master userfile and which will bots will be passive and accept the
-shared userfile.
-
-Yourbot will send userfiles to any others set to botattr +s.
-Yourbot will accept userfiles from any bot set to botattr +p.
-
-Active/aggressive bots send userfiles to link bots with the +s botattr flag.
-If those bots have the botattr of such an active bot set to +p, then they
-will passively accept the aggressive sender's userfile.
-
-In yourbot, setting slavebot +s will not make slavebot accept yourbot's
-userfile.  It will only make yourbot attempt to send your userfile to
-slavebot if they link.
-
-In yourbot, setting masterbot +p will not make masterbot send its userfile
-to yourbot.  The +p flag only gives masterbot permission to send yourbot a
-userfile, if masterbot chooses to send one.
-
-If you set slavebot +s, then yourbot will try to send slavebot your
-userfile, once a minute until a successful transfer is made.  If slavebot has
-not given you write/send permission by adding the +p for yourbot, then
-slavebot will refuse to accept yourbot's repeated offer to send.  Each and
-every minute you will see this message repeated on yourbot's console:
-
-<yourbot> [04:54] User file rejected by Slavebot: You are not marked for
-sharing with me.
-
-With these setting in yourbot:
-     masterbot +p  [yourbot will be passive with masterbot]
-     slavebot +s   [yourbot will be aggressive with slavebot]
-
-On connection to slavebot, slavebot does not ask yourbot to send it
-userfile.  Yourbot is aggressive in relation to slavebot and on linking,
-yourbot automatically attempts to send its userfile to slavebot without any
-request and will try to do so every 60 seconds until slavebot accepts the
-userfile and a successful transfer is completed.
-
-On connection to masterbot, yourbot does not ask master to send.  If
-masterbot decides to send, yourbot gives permission and will accept any
-userfile masterbot might send.
-
-If the flags in both bots do not make a +s+p pair, the bots will link but
-will not share.  If the +s+p pair is set properly, but the userfile transfer
-fails for some reason, the bots will unlink.  If with has a +h or +a hub
-flag set for the other, that bot will seek to relink and upon connection,
-another attempt to share will be made.  If successful, the bots will then
-stay linked and all will be well with the world.  :)
-
-
-
-Note that by sharing user records, you also share automatically bans and
-ignores (globally or channel specific) with the other bot. Botflags are
-*not* shared.
+  Note that by sharing user records, bans, invites, exempts and
+  ignores will automatically be shared. Botflags are *not* shared.
 
 
 
 Hope that this document helped you in some way...
 
-
-The Dev-Team..
+The Dev-Team
\ No newline at end of file
Index: eggdrop1.6/doc/UPDATES1.6
diff -u eggdrop1.6/doc/UPDATES1.6:1.279 eggdrop1.6/doc/UPDATES1.6:1.280
--- eggdrop1.6/doc/UPDATES1.6:1.279	Fri Dec 28 23:52:34 2001
+++ eggdrop1.6/doc/UPDATES1.6	Sat Dec 29 15:46:29 2001
@@ -1,12 +1,13 @@
-$Id: UPDATES1.6,v 1.279 2001/12/29 05:52:34 guppy Exp $
+$Id: UPDATES1.6,v 1.280 2001/12/29 21:46:29 guppy Exp $
 
 Changes in eggdrop: (since v1.6.0)
 ----------------------------------
 
 1.6.8
 Found by  Fixed by  What...
+          Wcc       updated doc/BOTNET and added doc/first_script.txt
           Wcc       removed some old debugging information
-various   zip       prevent the bot from loosing channel flags when allow-resync is set
+various   zip       prevent the bot from losing channel flags when allow-resync is set
           Wcc       some small cosmetic changes
           Wcc       added $hand-len for scripters to get the current length of handles from
                     src/eggdrop.h (this setting does not adjust handle lengths however)
Index: eggdrop1.6/doc/first_script.txt
diff -u /dev/null eggdrop1.6/doc/first_script.txt:1.1
--- /dev/null	Sat Dec 29 15:46:40 2001
+++ eggdrop1.6/doc/first_script.txt	Sat Dec 29 15:46:29 2001
@@ -0,0 +1,89 @@
+YOUR FIRST EGGDROP SCRIPT
+
+So you want to write an eggdrop script, but you don't really know where to
+begin. This file will give you a very basic idea about what eggdrop scripting
+is like. There are far too many topics to be covered all at once, but this may
+help you get started with your own scripts.
+
+This guide assumes you know a bit about eggdrops and irc. You should have
+already installed eggdrop. The bot should not be on any important or busy
+channels (development bots can be annoying if your script has bugs). If you
+plan on doing a lot of development, enable the .tcl and .set commands, and
+make sure nobody else has access to your bot. The .tcl and .set commands are
+helpful in debugging and testing your code.
+
+First, read through the script. You may be unfamiliar with some of the commands,
+especially if you haven't at least browsed through tcl-commands.doc. You may
+find it helpful to open up tcl-commands.doc in another window so that you can
+immediately look up commands you don't know.
+
+Then, open up another window and copy the script into its own file. If you have
+the .tcl command enabled, you can type '.tcl source scripts/yourfile.tcl' to
+load it. Otherwise, add it to your config file like normal and '.rehash' or
+'.restart' your bot.
+
+From your own irc client, join the bot's channel and type some lines that start
+with "hello". Example: hello I love you won't you tell me your name
+
+After your thrill abates, try playing around with your copy of the script. Get
+it to change the text it says, make it send notices instead of messages. Try
+changing the names of some variables (uhost -> userhost maybe).
+
+
+#
+# Here's the start of the script.
+# The '#' in tcl means this line is a comment and doesn't get executed.
+#
+
+#
+# Most scripts start off with a configuration section.
+#
+
+# Change this to the channel you want this script to work on.
+set our_chan "#baa"
+
+# After configuration, scripts generally do a bit of initialization work.
+# This could include checking the validity of the config variables, setting
+# timers, loading helper scripts, establishing database connections, or
+# most frequently, creating our eggdrop binds.
+#
+# A bind lets you attach your script to events that eggdrop encounters. Events
+# include irc events (someone joining a channel, talking, etc), botnet events,
+# and internal events (like receiving signals via the kill command).
+#
+
+# This bind will make eggdrop call "my_talk_handler" whenever someone
+# says hello on one of our channels.
+bind pub - hello my_talk_handler
+
+# Here is where we define "my_talk_handler"
+proc my_talk_handler {nick uhost hand chan text} {
+	#
+	# nick - the person's nickname
+	# uhost - the person's user at host
+	# hand - the person's bothandle (if he is a valid user)
+	# chan - the channel this event happened on
+	# text - the text the person said (not counting the trigger word)
+	#
+	# You can name these variables any way you want, but these names
+	# are pretty much standard.
+	#
+
+	# The 'global' command imports global variables into our local scope.
+	# Any variable set outside of a procedure (like in the config section)
+	# is a global variable.
+	global our_chan
+
+	# We only want to respond on the $our_chan channel.
+	if {$chan != $our_chan} {
+		return 0
+	}
+
+	# The putserv commands lets us send text to the server.
+	putserv "privmsg $chan :$text too!"
+
+	# All done! Log this command by returning 1.
+	return 1
+}
+
+# Here's the end of the script.
Index: eggdrop1.6/src/patch.h
diff -u eggdrop1.6/src/patch.h:1.657 eggdrop1.6/src/patch.h:1.658
--- eggdrop1.6/src/patch.h:1.657	Sat Dec 29 15:06:38 2001
+++ eggdrop1.6/src/patch.h	Sat Dec 29 15:46:29 2001
@@ -10,7 +10,7 @@
  * statement, leave the rest of the file alone, this allows better
  * overlapping patches.
  *
- * $Id: patch.h,v 1.657 2001/12/29 21:06:38 guppy Exp $
+ * $Id: patch.h,v 1.658 2001/12/29 21:46:29 guppy Exp $
  */
 /*
  * Copyright (C) 1997 Robey Pointer
@@ -41,12 +41,12 @@
  *
  *
  */
-patch("1009659608");		/* current unixtime */
+patch("1009662150");		/* current unixtime */
 /*
  *
  *
  */
-patch("transfer_revert");
+patch("yet_more_doc_updates");
 /*
  *
  *
----------------------- End of diff -----------------------



More information about the Changes mailing list