Skip to content
Snippets Groups Projects
Commit 6cf6618b authored by cvs2git's avatar cvs2git
Browse files

This commit was manufactured by cvs2svn to create tag 'goodbuild_linux'.

parent 048aa226
No related branches found
No related merge requests found
# The "checkoutlist" file is used to support additional version controlled
# administrative files in $CVSROOT/CVSROOT, such as template files.
#
# The first entry on a line is a filename which will be checked out from
# the corresponding RCS file in the $CVSROOT/CVSROOT directory.
# The remainder of the line is an error message to use if the file cannot
# be checked out.
#
# File format:
#
# [<whitespace>]<filename><whitespace><error message><end-of-line>
#
# comment lines begin with '#'
# The "commitinfo" file is used to control pre-commit checks.
# The filter on the right is invoked with the repository and a list
# of files to check. A non-zero exit of the filter program will
# cause the commit to be aborted.
#
# The first entry on a line is a regular expression which is tested
# against the directory that the change is being committed to, relative
# to the $CVSROOT. For the first match that is found, then the remainder
# of the line is the name of the filter to run.
#
# If the repository name does not match any of the regular expressions in this
# file, the "DEFAULT" line is used, if it is specified.
#
# If the name "ALL" appears as a regular expression it is always used
# in addition to the first matching regex or "DEFAULT".
# Set this to "no" if pserver shouldn't check system users/passwords
#SystemAuth=no
# Set `PreservePermissions' to `yes' to save file status information
# in the repository.
#PreservePermissions=no
# Set `TopLevelAdmin' to `yes' to create a CVS directory at the top
# level of the new working directory when using the `cvs checkout'
# command.
#TopLevelAdmin=no
# Requires CVS v1.12+
UseNewInfoFmtStrings=yes
\ No newline at end of file
# This file affects handling of files based on their names.
#
# The -t/-f options allow one to treat directories of files
# as a single file, or to transform a file in other ways on
# its way in and out of CVS.
#
# The -m option specifies whether CVS attempts to merge files.
#
# The -k option specifies keyword expansion (e.g. -kb for binary).
#
# Format of wrapper file ($CVSROOT/CVSROOT/cvswrappers or .cvswrappers)
#
# wildcard [option value][option value]...
#
# where option is one of
# -f from cvs filter value: path to filter
# -t to cvs filter value: path to filter
# -m update methodology value: MERGE or COPY
# -k expansion mode value: b, o, kkv, &c
#
# and value is a single-quote delimited value.
# For example:
#*.gif -k 'b'
# The "editinfo" file is used to allow verification of logging
# information. It works best when a template (as specified in the
# rcsinfo file) is provided for the logging procedure. Given a
# template with locations for, a bug-id number, a list of people who
# reviewed the code before it can be checked in, and an external
# process to catalog the differences that were code reviewed, the
# following test can be applied to the code:
#
# Making sure that the entered bug-id number is correct.
# Validating that the code that was reviewed is indeed the code being
# checked in (using the bug-id number or a seperate review
# number to identify this particular code set.).
#
# If any of the above test failed, then the commit would be aborted.
#
# Actions such as mailing a copy of the report to each reviewer are
# better handled by an entry in the loginfo file.
#
# One thing that should be noted is the the ALL keyword is not
# supported. There can be only one entry that matches a given
# repository.
# The "loginfo" file controls where "cvs commit" log information
# is sent. The first entry on a line is a regular expression which must match
# the directory that the change is being made to, relative to the
# $CVSROOT. If a match is found, then the remainder of the line is a filter
# program that should expect log information on its standard input.
#
# If the repository name does not match any of the regular expressions in this
# file, the "DEFAULT" line is used, if it is specified.
#
# If the name ALL appears as a regular expression it is always used
# in addition to the first matching regex or DEFAULT.
#
# You may specify a format string as part of the
# filter. The string is composed of a `%' followed
# by a single format character, or followed by a set of format
# characters surrounded by `{' and `}' as separators. The format
# characters are:
#
# s = file name
# V = old version number (pre-checkin)
# v = new version number (post-checkin)
#
# For example:
#DEFAULT (echo ""; id; echo %s; date; cat) >> $CVSROOT/CVSROOT/commitlog
# or
#DEFAULT (echo ""; id; echo %{sVv}; date; cat) >> $CVSROOT/CVSROOT/commitlog
ALL (echo %p %{sVv}; cat) | smbutil -o -i "-tCVS commit" "-s%p/%s" -f$USER i /sbbs/data/subs/syncprog;sync
ALL jsexec -c /sbbs/ctrl ircmsg -s bbs.synchro.net -p 5050 -c \#synchronet -n cvs_$USER -x "^In directory cvs" -x "^Modified Files:\$" -x "^Log Message:\$"
ALL jsexec -c /sbbs/ctrl gnats_cvs $USER cvs justme
# Three different line formats are valid:
# key -a aliases...
# key [options] directory
# key [options] directory files...
#
# Where "options" are composed of:
# -i prog Run "prog" on "cvs commit" from top-level of module.
# -o prog Run "prog" on "cvs checkout" of module.
# -e prog Run "prog" on "cvs export" of module.
# -t prog Run "prog" on "cvs rtag" of module.
# -u prog Run "prog" on "cvs update" of module.
# -d dir Place module in directory "dir" instead of module name.
# -l Top-level directory only -- do not recurse.
#
# NOTE: If you change any of the "Run" options above, you'll have to
# release and re-checkout any working directories of these modules.
#
# And "directory" is a path to a directory relative to $CVSROOT.
#
# The "-a" option specifies an alias. An alias is interpreted as if
# everything on the right of the "-a" had been typed on the command line.
#
# You can encode a module within a module by using the special '&'
# character to interpose another module into the current module. This
# can be useful for creating a module that consists of many directories
# spread out over the entire source repository.
lib-win32 -a lib/mozilla/js/win32.release lib/mozilla/nspr/win32.release lib/microsoft lib/cryptlib
lib-win32.release -a lib/mozilla/js/win32.release lib/mozilla/nspr/win32.release lib/microsoft lib/cryptlib
lib-win32.debug -a lib/mozilla/js/win32.debug lib/mozilla/nspr/win32.release lib/microsoft lib/cryptlib
lib-linux -a lib/mozilla/js/linux.release lib/mozilla/nspr/linux.release lib/cryptlib/linux.release
lib-linux.release -a lib/mozilla/js/linux.release lib/mozilla/nspr/linux.release lib/cryptlib/linux.release
lib-linux.debug -a lib/mozilla/js/linux.debug lib/mozilla/nspr/linux.debug lib/cryptlib/linux.release
lib-freebsd -a lib/mozilla/js/freebsd.release lib/mozilla/nspr/freebsd.release lib/cryptlib/freebsd.release
lib-freebsd.release -a lib/mozilla/js/freebsd.release lib/mozilla/nspr/freebsd.release lib/cryptlib/freebsd.release
lib-freebsd.debug -a lib/mozilla/js/freebsd.debug lib/mozilla/nspr/freebsd.debug lib/cryptlib/freebsd.release
lib-openbsd -a lib/mozilla/js/openbsd.release lib/mozilla/nspr/openbsd.release lib/cryptlib/openbsd.release
lib-openbsd.release -a lib/mozilla/js/openbsd.release lib/mozilla/nspr/openbsd.release lib/cryptlib/openbsd.release
lib-openbsd.debug -a lib/mozilla/js/openbsd.debug lib/mozilla/nspr/openbsd.debug lib/cryptlib/openbsd.release
lib-netbsd -a lib/mozilla/js/netbsd.release lib/mozilla/nspr/netbsd.release lib/cryptlib/netbsd.release
lib-netbsd.release -a lib/mozilla/js/netbsd.release lib/mozilla/nspr/netbsd.release lib/cryptlib/netbsd.release
lib-netbsd.debug -a lib/mozilla/js/netbsd.debug lib/mozilla/nspr/netbsd.debug lib/cryptlib/netbsd.release
src-sbbs3 -a src/build src/sbbs3 src/xpdev src/smblib src/uifc include src/conio src/sexpots src/comio
run-sbbs3 -a ctrl text exec xtrn node1 node2 node3 node4 docs web
ircd -a exec/dnshelper.js exec/irclib.js exec/ircd.js exec/ircd_server.js exec/ircd_channel.js exec/ircd_user.js exec/ircd_unreg.js
install install
include include
lib lib
src src
docs docs
ctrl ctrl
text text
exec exec
xtrn xtrn
web web
# The "notify" file controls where notifications from watches set by
# "cvs watch add" or "cvs edit" are sent. The first entry on a line is
# a regular expression which is tested against the directory that the
# change is being made to, relative to the $CVSROOT. If it matches,
# then the remainder of the line is a filter program that should contain
# one occurrence of %s for the user to notify, and information on its
# standard input.
#
# "ALL" or "DEFAULT" can be used in place of the regular expression.
#
# For example:
#ALL mail %s -s "CVS notification"
# The "postadmin" file is called after the "admin" command finishes# processing a directory.#
# If any format strings are present in the filter, they will be replaced# as follows:
# %p = path relative to repository
# %r = repository (path portion of $CVSROOT)
#
# The first entry on a line is a regular expression which is tested
# against the directory that the change is being committed to, relative
# to the $CVSROOT. For the first match that is found, then the remainder
# of the line is the name of the filter to run.
#
# If the repository name does not match any of the regular expressions in this
# file, the "DEFAULT" line is used, if it is specified.
#
# If the name "ALL" appears as a regular expression it is always used
# in addition to the first matching regex or "DEFAULT".
# The "postproxy" file is called from a secondary server as soon as
# the secondary server closes its connection to the primary server.
# This script might, for example, be used to shut down a dial up
# or VPN connection to the primary server's network.
#
# If any format strings are present in the filter, they will be replaced# as follows:
# %p = path relative to repository (currently always ".")
# %r = repository (path portion of $CVSROOT)
#
# The first entry on a line is a regular expression which is tested
# against the directory that the change is being committed to, relative
# to the $CVSROOT. For the first match that is found, then the remainder
# of the line is the name of the filter to run.
#
# If the repository name does not match any of the regular expressions in this
# file, the "DEFAULT" line is used, if it is specified.
#
# If the name "ALL" appears as a regular expression it is always used
# in addition to the first matching regex or "DEFAULT".
# The "posttag" file is called after the "tag" command finishes# processing a directory.#
# If any format strings are present in the filter, they will be replaced as follows:
# %b = branch mode = "?" (delete ops - unknown) | "T" (branch) | "N" (not branch)
# %o = operation = "add" | "mov" | "del"
# %p = path relative to repository
# %r = repository (path portion of $CVSROOT)
# %t = tagname
# %{sVv} = attribute list = file name, old version tag will be deleted
# from, new version tag will be added to (or deleted from, but
# this feature is deprecated. When either old or new revision is
# unknown, doesn't exist, or isn't applicable, the string "NONE"
# will be placed on the command line.
#
# Note that %{sVv} is a list operator and not all elements are necessary.
# Thus %{sV} is a legal format string, but will only be replaced with file
# name and old revision. it also generates multiple arguments for each file
# being operated upon. i.e. if two files, file1 & file2, are having a tag
# moved from version 1.1 to version 1.1.2.9, %{sVv} will generate the
# following six arguments in this order: file1, 1.1, 1.1.2.9, file2, 1.1,
# 1.1.2.9.
#
# The first entry on a line is a regular expression which is tested
# against the directory that the change is being committed to, relative
# to the $CVSROOT. For the first match that is found, then the remainder
# of the line is the name of the filter to run.
#
# If the repository name does not match any of the regular expressions in this
# file, the "DEFAULT" line is used, if it is specified.
#
# If the name "ALL" appears as a regular expression it is always used
# in addition to the first matching regex or "DEFAULT".
# The "postwatch" file is called after any command finishes writing new
# file attibute (watch/edit) information in a directory.
#
# If any format strings are present in the filter, they will be replaced# as follows:
# %p = path relative to repository
# %r = repository (path portion of $CVSROOT)
#
# The first entry on a line is a regular expression which is tested
# against the directory that the change is being committed to, relative
# to the $CVSROOT. For the first match that is found, then the remainder
# of the line is the name of the filter to run.
#
# If the repository name does not match any of the regular expressions in this
# file, the "DEFAULT" line is used, if it is specified.
#
# If the name "ALL" appears as a regular expression it is always used
# in addition to the first matching regex or "DEFAULT".
# The "preproxy" file is called form the secondary server as soon as
# the secondary server determines that it will be proxying a write
# command to a primary server and immediately before it opens a
# connection to the primary server. This script might, for example, be
# used to launch a dial up or VPN connection to the primary server's
# network.
#
# If any format strings are present in the filter, they will be replaced# as follows:
# %p = path relative to repository (currently always ".")
# %r = repository (path portion of $CVSROOT)
#
# The first entry on a line is a regular expression which is tested
# against the directory that the change is being committed to, relative
# to the $CVSROOT. For the first match that is found, then the remainder
# of the line is the name of the filter to run.
#
# If the repository name does not match any of the regular expressions in this
# file, the "DEFAULT" line is used, if it is specified.
#
# If the name "ALL" appears as a regular expression it is always used
# in addition to the first matching regex or "DEFAULT".
# The "rcsinfo" file is used to control templates with which the editor
# is invoked on commit and import.
#
# The first entry on a line is a regular expression which is tested
# against the directory that the change is being made to, relative to the
# $CVSROOT. For the first match that is found, then the remainder of the
# line is the name of the file that contains the template.
#
# If the repository name does not match any of the regular expressions in this
# file, the "DEFAULT" line is used, if it is specified.
#
# If the name "ALL" appears as a regular expression it is always used
# in addition to the first matching regex or "DEFAULT".
# The "taginfo" file is used to control pre-tag checks.
# The filter on the right is invoked with the following arguments:
#
# $1 -- tagname
# $2 -- operation "add" for tag, "mov" for tag -F, and "del" for tag -d
# $3 -- repository
# $4-> file revision [file revision ...]
#
# A non-zero exit of the filter program will cause the tag to be aborted.
#
# The first entry on a line is a regular expression which is tested
# against the directory that the change is being committed to, relative
# to the $CVSROOT. For the first match that is found, then the remainder
# of the line is the name of the filter to run.
#
# If the repository name does not match any of the regular expressions in this
# file, the "DEFAULT" line is used, if it is specified.
#
# If the name "ALL" appears as a regular expression it is always used
# in addition to the first matching regex or "DEFAULT".
# The "verifymsg" file is used to allow verification of logging
# information. It works best when a template (as specified in the
# rcsinfo file) is provided for the logging procedure. Given a
# template with locations for, a bug-id number, a list of people who
# reviewed the code before it can be checked in, and an external
# process to catalog the differences that were code reviewed, the
# following test can be applied to the code:
#
# Making sure that the entered bug-id number is correct.
# Validating that the code that was reviewed is indeed the code being
# checked in (using the bug-id number or a seperate review
# number to identify this particular code set.).
#
# If any of the above test failed, then the commit would be aborted.
#
# Actions such as mailing a copy of the report to each reviewer are
# better handled by an entry in the loginfo file.
#
# One thing that should be noted is the the ALL keyword is not
# supported. There can be only one entry that matches a given
# repository.
; $Id$
; Alias User Name, number, or external forwarding address
; ------------------- -------------------------------------------------
; wildcards (*) are allowed wildcards (*) are allowed
; can be <name> can be <name>
; or <name>@<address> or <name>@<address>
; or <name>@<address>:<port>
sysop 1
root 1
abuse 1
sysadmin 1
webmaster 1
postmaster 1
WH Mnemonic Prompts High
G Mnemonic Prompts Low
WH Mnemonic Commands
WH4 String Input Inverse Text
RH Error/Warning Message
WH Node Number in Node Status
GH User Name in Node Status
G Node Status
BH File Name in Listings
M File Points in Listings
G File Descriptions in Listings
YH File Listings Header Box
B File Listings Title Underline
GH Chat Text Input Locally
G Chat Text Input Remotely
W Mult-node Chat Text Input
WH External Programs (default attribute)
; $Id$
; This file is for use with the Synchronet Web Server's CGI support.
; Contains a list of system environment variables to pass to the CGI processes.
; The format is (all key=value pairs are optional):
; [variable]
; default = default_value
; value = override_value
; prepend = prepended_string
; append = appended_string
; Unix/common vars
[PATH]
[SHELL]
[HOSTTYPE]
[VENDOR]
[OSTYPE]
[PWD]
[USER]
[GROUP]
[TEMP]
[TMP]
[LD_LIBRARY_PATH]
[TZ]
; Windows vars
[COMPUTERNAME]
[OS]
[SystemDrive]
[SystemRoot]
[windir]
; Required for PHP-CGI
[REDIRECT_STATUS]
value=200
\ No newline at end of file
File deleted
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment