-14

CVSROOT/checkoutlist

reviewed

··· 1 1 - # The "checkoutlist" file is used to support additional version controlled 2 2 - # administrative files in $CVSROOT/CVSROOT, such as template files. 3 3 - # 4 4 - # The first entry on a line is a filename which will be checked out from 5 5 - # the corresponding RCS file in the $CVSROOT/CVSROOT directory. 6 6 - # The remainder of the line is an error message to use if the file cannot 7 7 - # be checked out. 8 8 - # 9 9 - # File format: 10 10 - # 11 11 - # [<whitespace>]<filename><whitespace><error message><end-of-line> 12 12 - # 13 13 - # comment lines begin with '#' 14 14 - syncmail

-15

CVSROOT/commitinfo

reviewed

··· 1 1 - # The "commitinfo" file is used to control pre-commit checks. 2 2 - # The filter on the right is invoked with the repository and a list 3 3 - # of files to check. A non-zero exit of the filter program will 4 4 - # cause the commit to be aborted. 5 5 - # 6 6 - # The first entry on a line is a regular expression which is tested 7 7 - # against the directory that the change is being committed to, relative 8 8 - # to the $CVSROOT. For the first match that is found, then the remainder 9 9 - # of the line is the name of the filter to run. 10 10 - # 11 11 - # If the repository name does not match any of the regular expressions in this 12 12 - # file, the "DEFAULT" line is used, if it is specified. 13 13 - # 14 14 - # If the name "ALL" appears as a regular expression it is always used 15 15 - # in addition to the first matching regex or "DEFAULT".

-14

CVSROOT/config

reviewed

··· 1 1 - # Set this to "no" if pserver shouldn't check system users/passwords 2 2 - #SystemAuth=no 3 3 - 4 4 - # Set `PreservePermissions' to `yes' to save file status information 5 5 - # in the repository. 6 6 - #PreservePermissions=no 7 7 - 8 8 - # Set `TopLevelAdmin' to `yes' to create a CVS directory at the top 9 9 - # level of the new working directory when using the `cvs checkout' 10 10 - # command. 11 11 - #TopLevelAdmin=no 12 12 - 13 13 - # use new info format 14 14 - UseNewInfoFmtStrings=yes

-23

CVSROOT/cvswrappers

reviewed

··· 1 1 - # This file affects handling of files based on their names. 2 2 - # 3 3 - # The -t/-f options allow one to treat directories of files 4 4 - # as a single file, or to transform a file in other ways on 5 5 - # its way in and out of CVS. 6 6 - # 7 7 - # The -m option specifies whether CVS attempts to merge files. 8 8 - # 9 9 - # The -k option specifies keyword expansion (e.g. -kb for binary). 10 10 - # 11 11 - # Format of wrapper file ($CVSROOT/CVSROOT/cvswrappers or .cvswrappers) 12 12 - # 13 13 - # wildcard [option value][option value]... 14 14 - # 15 15 - # where option is one of 16 16 - # -f from cvs filter value: path to filter 17 17 - # -t to cvs filter value: path to filter 18 18 - # -m update methodology value: MERGE or COPY 19 19 - # -k expansion mode value: b, o, kkv, &c 20 20 - # 21 21 - # and value is a single-quote delimited value. 22 22 - # For example: 23 23 - #*.gif -k 'b'

-21

CVSROOT/editinfo

reviewed

··· 1 1 - # The "editinfo" file is used to allow verification of logging 2 2 - # information. It works best when a template (as specified in the 3 3 - # rcsinfo file) is provided for the logging procedure. Given a 4 4 - # template with locations for, a bug-id number, a list of people who 5 5 - # reviewed the code before it can be checked in, and an external 6 6 - # process to catalog the differences that were code reviewed, the 7 7 - # following test can be applied to the code: 8 8 - # 9 9 - # Making sure that the entered bug-id number is correct. 10 10 - # Validating that the code that was reviewed is indeed the code being 11 11 - # checked in (using the bug-id number or a seperate review 12 12 - # number to identify this particular code set.). 13 13 - # 14 14 - # If any of the above test failed, then the commit would be aborted. 15 15 - # 16 16 - # Actions such as mailing a copy of the report to each reviewer are 17 17 - # better handled by an entry in the loginfo file. 18 18 - # 19 19 - # One thing that should be noted is the the ALL keyword is not 20 20 - # supported. There can be only one entry that matches a given 21 21 - # repository.

-38

CVSROOT/loginfo

reviewed

··· 1 1 - # The "loginfo" file controls where "cvs commit" log information 2 2 - # is sent. The first entry on a line is a regular expression which must match 3 3 - # the directory that the change is being made to, relative to the 4 4 - # $CVSROOT. If a match is found, then the remainder of the line is a filter 5 5 - # program that should expect log information on its standard input. 6 6 - # 7 7 - # If the repository name does not match any of the regular expressions in this 8 8 - # file, the "DEFAULT" line is used, if it is specified. 9 9 - # 10 10 - # If the name ALL appears as a regular expression it is always used 11 11 - # in addition to the first matching regex or DEFAULT. 12 12 - # 13 13 - # You may specify a format string as part of the 14 14 - # filter. The string is composed of a `%' followed 15 15 - # by a single format character, or followed by a set of format 16 16 - # characters surrounded by `{' and `}' as separators. The format 17 17 - # characters are: 18 18 - # 19 19 - # s = file name 20 20 - # V = old version number (pre-checkin) 21 21 - # v = new version number (post-checkin) 22 22 - # 23 23 - # For example: 24 24 - #DEFAULT (echo ""; id; echo %s; date; cat) >> $CVSROOT/CVSROOT/commitlog 25 25 - # or 26 26 - #DEFAULT (echo ""; id; echo %{sVv}; date; cat) >> $CVSROOT/CVSROOT/commitlog 27 27 - CVSROOT /usr/bin/syncmail -C4 -u %1{sVv} bjorn@haxx.se 28 28 - ^apps /usr/bin/syncmail -C4 -u -S "$USER: " %1{sVv} rockbox-cvs@cool.haxx.se 29 29 - ^flash /usr/bin/syncmail -C4 -u -S "$USER: " %1{sVv} rockbox-cvs@cool.haxx.se 30 30 - ^firmware /usr/bin/syncmail -C4 -u -S "$USER: " %1{sVv} rockbox-cvs@cool.haxx.se 31 31 - ^docs /usr/bin/syncmail -C4 -u -S "$USER: " %1{sVv} rockbox-cvs@cool.haxx.se 32 32 - ^uisimulator /usr/bin/syncmail -C4 -u -S "$USER: " %1{sVv} rockbox-cvs@cool.haxx.se 33 33 - ^tools /usr/bin/syncmail -C4 -u -S "$USER: " %1{sVv} rockbox-cvs@cool.haxx.se 34 34 - ^gdb /usr/bin/syncmail -C4 -u -S "$USER: " %1{sVv} rockbox-cvs@cool.haxx.se 35 35 - ^bootloader /usr/bin/syncmail -C4 -u -S "$USER: " %1{sVv} rockbox-cvs@cool.haxx.se 36 36 - ^wps /usr/bin/syncmail -C4 -u -S "$USER: " %1{sVv} rockbox-cvs@cool.haxx.se 37 37 - ^manual /usr/bin/syncmail -C4 -u -S "$USER: " %1{sVv} rockbox-cvs@cool.haxx.se 38 38 - ^rbutil /usr/bin/syncmail -C4 -u -S "$USER: " %1{sVv} rockbox-cvs@cool.haxx.se

-31

CVSROOT/modules

reviewed

··· 1 1 - # Three different line formats are valid: 2 2 - # key -a aliases... 3 3 - # key [options] directory 4 4 - # key [options] directory files... 5 5 - # 6 6 - # Where "options" are composed of: 7 7 - # -i prog Run "prog" on "cvs commit" from top-level of module. 8 8 - # -o prog Run "prog" on "cvs checkout" of module. 9 9 - # -e prog Run "prog" on "cvs export" of module. 10 10 - # -t prog Run "prog" on "cvs rtag" of module. 11 11 - # -u prog Run "prog" on "cvs update" of module. 12 12 - # -d dir Place module in directory "dir" instead of module name. 13 13 - # -l Top-level directory only -- do not recurse. 14 14 - # 15 15 - # NOTE: If you change any of the "Run" options above, you'll have to 16 16 - # release and re-checkout any working directories of these modules. 17 17 - # 18 18 - # And "directory" is a path to a directory relative to $CVSROOT. 19 19 - # 20 20 - # The "-a" option specifies an alias. An alias is interpreted as if 21 21 - # everything on the right of the "-a" had been typed on the command line. 22 22 - # 23 23 - # You can encode a module within a module by using the special '&' 24 24 - # character to interpose another module into the current module. This 25 25 - # can be useful for creating a module that consists of many directories 26 26 - # spread out over the entire source repository. 27 27 - 28 28 - rockbox &apps &firmware &docs &tools &fonts &wps 29 29 - rockbox-devel &apps &flash &firmware &fonts &bootloader &docs &tools &uisimulator &gdb &wps &manual 30 30 - rockbox-all &apps &flash &firmware &fonts &bootloader &docs &tools &uisimulator &gdb &www &wps &manual 31 31 - website &www &docs

-12

CVSROOT/notify

reviewed

··· 1 1 - # The "notify" file controls where notifications from watches set by 2 2 - # "cvs watch add" or "cvs edit" are sent. The first entry on a line is 3 3 - # a regular expression which is tested against the directory that the 4 4 - # change is being made to, relative to the $CVSROOT. If it matches, 5 5 - # then the remainder of the line is a filter program that should contain 6 6 - # one occurrence of %s for the user to notify, and information on its 7 7 - # standard input. 8 8 - # 9 9 - # "ALL" or "DEFAULT" can be used in place of the regular expression. 10 10 - # 11 11 - # For example: 12 12 - #ALL mail %s -s "CVS notification"

-13

CVSROOT/rcsinfo

reviewed

··· 1 1 - # The "rcsinfo" file is used to control templates with which the editor 2 2 - # is invoked on commit and import. 3 3 - # 4 4 - # The first entry on a line is a regular expression which is tested 5 5 - # against the directory that the change is being made to, relative to the 6 6 - # $CVSROOT. For the first match that is found, then the remainder of the 7 7 - # line is the name of the file that contains the template. 8 8 - # 9 9 - # If the repository name does not match any of the regular expressions in this 10 10 - # file, the "DEFAULT" line is used, if it is specified. 11 11 - # 12 12 - # If the name "ALL" appears as a regular expression it is always used 13 13 - # in addition to the first matching regex or "DEFAULT".

-217

CVSROOT/syncmail

reviewed

··· 1 1 - #! /usr/bin/python 2 2 - # -*- Python -*- 3 3 - 4 4 - """Complicated notification for CVS checkins. 5 5 - 6 6 - This script is used to provide email notifications of changes to the CVS 7 7 - repository. These email changes will include context diffs of the changes. 8 8 - Really big diffs will be trimmed. 9 9 - 10 10 - This script is run from a CVS loginfo file (see $CVSROOT/CVSROOT/loginfo). To 11 11 - set this up, create a loginfo entry that looks something like this: 12 12 - 13 13 - mymodule /path/to/this/script %%s some-email-addr@your.domain 14 14 - 15 15 - In this example, whenever a checkin that matches `mymodule' is made, this 16 16 - script is invoked, which will generate the diff containing email, and send it 17 17 - to some-email-addr@your.domain. 18 18 - 19 19 - Note: This module used to also do repository synchronizations via 20 20 - rsync-over-ssh, but since the repository has been moved to SourceForge, 21 21 - this is no longer necessary. The syncing functionality has been ripped 22 22 - out in the 3.0, which simplifies it considerably. Access the 2.x versions 23 23 - to refer to this functionality. Because of this, the script is misnamed. 24 24 - 25 25 - It no longer makes sense to run this script from the command line. Doing so 26 26 - will only print out this usage information. 27 27 - 28 28 - Usage: 29 29 - 30 30 - %(PROGRAM)s [options] <%%S> email-addr [email-addr ...] 31 31 - 32 32 - Where options is: 33 33 - 34 34 - --cvsroot=<path> 35 35 - Use <path> as the environment variable CVSROOT. Otherwise this 36 36 - variable must exist in the environment. 37 37 - 38 38 - --help 39 39 - -h 40 40 - Print this text. 41 41 - 42 42 - --context=# 43 43 - -C # 44 44 - Include # lines of context around lines that differ (default: 2). 45 45 - 46 46 - -c 47 47 - Produce a context diff (default). 48 48 - 49 49 - -u 50 50 - Produce a unified diff (smaller, but harder to read). 51 51 - 52 52 - -U user 53 53 - Mark diff as made by user. 54 54 - 55 55 - <%%S> 56 56 - CVS %%s loginfo expansion. When invoked by CVS, this will be a single 57 57 - string containing the directory the checkin is being made in, relative 58 58 - to $CVSROOT, followed by the list of files that are changing. If the 59 59 - %%s in the loginfo file is %%{sVv}, context diffs for each of the 60 60 - modified files are included in any email messages that are generated. 61 61 - 62 62 - email-addrs 63 63 - At least one email address. 64 64 - 65 65 - """ 66 66 - 67 67 - import os 68 68 - import sys 69 69 - import string 70 70 - import time 71 71 - import getopt 72 72 - 73 73 - # Notification command 74 74 - MAILCMD = '/bin/mail -s "%(username)s: %(SUBJECT)s" %(PEOPLE)s 2>&1 > /dev/null' 75 75 - 76 76 - # Diff trimming stuff 77 77 - DIFF_HEAD_LINES = 20 78 78 - DIFF_TAIL_LINES = 20 79 79 - DIFF_TRUNCATE_IF_LARGER = 1000 80 80 - 81 81 - PROGRAM = sys.argv[0] 82 82 - 83 83 - 84 84 -  85 85 - def usage(code, msg=''): 86 86 - print __doc__ % globals() 87 87 - if msg: 88 88 - print msg 89 89 - sys.exit(code) 90 90 - 91 91 - 92 92 -  93 93 - def calculate_diff(filespec, contextlines): 94 94 - try: 95 95 - file, oldrev, newrev = string.split(filespec, ',') 96 96 - except ValueError: 97 97 - # No diff to report 98 98 - return '***** Bogus filespec: %s' % filespec 99 99 - if oldrev == 'NONE': 100 100 - try: 101 101 - if os.path.exists(file): 102 102 - fp = open(file) 103 103 - else: 104 104 - update_cmd = 'cvs -fn update -r %s -p %s' % (newrev, file) 105 105 - fp = os.popen(update_cmd) 106 106 - lines = fp.readlines() 107 107 - fp.close() 108 108 - lines.insert(0, '--- NEW FILE: %s ---\n' % file) 109 109 - except IOError, e: 110 110 - lines = ['***** Error reading new file: ', 111 111 - str(e), '\n***** file: ', file, ' cwd: ', os.getcwd()] 112 112 - elif newrev == 'NONE': 113 113 - lines = ['--- %s DELETED ---\n' % file] 114 114 - else: 115 115 - # This /has/ to happen in the background, otherwise we'll run into CVS 116 116 - # lock contention. What a crock. 117 117 - if contextlines > 0: 118 118 - difftype = "-C " + str(contextlines) 119 119 - else: 120 120 - difftype = "-uN" 121 121 - diffcmd = '/usr/bin/cvs -f diff -kk %s -b -r %s -r %s %s' % ( 122 122 - difftype, oldrev, newrev, file) 123 123 - fp = os.popen(diffcmd) 124 124 - lines = fp.readlines() 125 125 - sts = fp.close() 126 126 - # ignore the error code, it always seems to be 1 :( 127 127 - ## if sts: 128 128 - ## return 'Error code %d occurred during diff\n' % (sts >> 8) 129 129 - if len(lines) > DIFF_TRUNCATE_IF_LARGER: 130 130 - removedlines = len(lines) - DIFF_HEAD_LINES - DIFF_TAIL_LINES 131 131 - del lines[DIFF_HEAD_LINES:-DIFF_TAIL_LINES] 132 132 - lines.insert(DIFF_HEAD_LINES, 133 133 - '[...%d lines suppressed...]\n' % removedlines) 134 134 - return string.join(lines, '') 135 135 - 136 136 - 137 137 -  138 138 - def blast_mail(mailcmd, filestodiff, contextlines): 139 139 - # cannot wait for child process or that will cause parent to retain cvs 140 140 - # lock for too long. Urg! 141 141 - if not os.fork(): 142 142 - # in the child 143 143 - # give up the lock you cvs thang! 144 144 - time.sleep(2) 145 145 - fp = os.popen(mailcmd, 'w') 146 146 - fp.write(sys.stdin.read()) 147 147 - fp.write('\n') 148 148 - # append the diffs if available 149 149 - for file in filestodiff: 150 150 - fp.write(calculate_diff(file, contextlines)) 151 151 - fp.write('\n') 152 152 - fp.close() 153 153 - # doesn't matter what code we return, it isn't waited on 154 154 - os._exit(0) 155 155 - 156 156 - 157 157 -  158 158 - # scan args for options 159 159 - def main(): 160 160 - contextlines = 2 161 161 - try: 162 162 - opts, args = getopt.getopt(sys.argv[1:], 'hC:cuU:', 163 163 - ['context=', 'cvsroot=', 'help']) 164 164 - except getopt.error, msg: 165 165 - usage(1, msg) 166 166 - 167 167 - username = 'unknown' 168 168 - 169 169 - # parse the options 170 170 - for opt, arg in opts: 171 171 - if opt in ('-h', '--help'): 172 172 - usage(0) 173 173 - elif opt == '--cvsroot': 174 174 - os.environ['CVSROOT'] = arg 175 175 - elif opt in ('-C', '--context'): 176 176 - contextlines = int(arg) 177 177 - elif opt == '-c': 178 178 - if contextlines <= 0: 179 179 - contextlines = 2 180 180 - elif opt == '-u': 181 181 - contextlines = 0 182 182 - elif opt == '-U': 183 183 - username = arg 184 184 - 185 185 - # What follows is the specification containing the files that were 186 186 - # modified. The argument actually must be split, with the first component 187 187 - # containing the directory the checkin is being made in, relative to 188 188 - # $CVSROOT, followed by the list of files that are changing. 189 189 - if not args: 190 190 - usage(1, 'No CVS module specified') 191 191 - SUBJECT = args[0] 192 192 - specs = string.split(args[0]) 193 193 - del args[0] 194 194 - 195 195 - # The remaining args should be the email addresses 196 196 - if not args: 197 197 - usage(1, 'No recipients specified') 198 198 - 199 199 - # Now do the mail command 200 200 - PEOPLE = string.join(args) 201 201 - mailcmd = MAILCMD % vars() 202 202 - 203 203 - print 'Mailing %s...' % PEOPLE 204 204 - if specs == ['-', 'Imported', 'sources']: 205 205 - return 206 206 - if specs[-3:] == ['-', 'New', 'directory']: 207 207 - del specs[-3:] 208 208 - print 'Generating notification message...' 209 209 - blast_mail(mailcmd, specs[1:], contextlines) 210 210 - print 'Generating notification message... done.' 211 211 - 212 212 - 213 213 -  214 214 - if __name__ == '__main__': 215 215 - main() 216 216 - sys.exit(0) 217 217 -

-20

CVSROOT/taginfo

reviewed

··· 1 1 - # The "taginfo" file is used to control pre-tag checks. 2 2 - # The filter on the right is invoked with the following arguments: 3 3 - # 4 4 - # $1 -- tagname 5 5 - # $2 -- operation "add" for tag, "mov" for tag -F, and "del" for tag -d 6 6 - # $3 -- repository 7 7 - # $4-> file revision [file revision ...] 8 8 - # 9 9 - # A non-zero exit of the filter program will cause the tag to be aborted. 10 10 - # 11 11 - # The first entry on a line is a regular expression which is tested 12 12 - # against the directory that the change is being committed to, relative 13 13 - # to the $CVSROOT. For the first match that is found, then the remainder 14 14 - # of the line is the name of the filter to run. 15 15 - # 16 16 - # If the repository name does not match any of the regular expressions in this 17 17 - # file, the "DEFAULT" line is used, if it is specified. 18 18 - # 19 19 - # If the name "ALL" appears as a regular expression it is always used 20 20 - # in addition to the first matching regex or "DEFAULT".

-21

CVSROOT/verifymsg

reviewed

··· 1 1 - # The "verifymsg" file is used to allow verification of logging 2 2 - # information. It works best when a template (as specified in the 3 3 - # rcsinfo file) is provided for the logging procedure. Given a 4 4 - # template with locations for, a bug-id number, a list of people who 5 5 - # reviewed the code before it can be checked in, and an external 6 6 - # process to catalog the differences that were code reviewed, the 7 7 - # following test can be applied to the code: 8 8 - # 9 9 - # Making sure that the entered bug-id number is correct. 10 10 - # Validating that the code that was reviewed is indeed the code being 11 11 - # checked in (using the bug-id number or a seperate review 12 12 - # number to identify this particular code set.). 13 13 - # 14 14 - # If any of the above test failed, then the commit would be aborted. 15 15 - # 16 16 - # Actions such as mailing a copy of the report to each reviewer are 17 17 - # better handled by an entry in the loginfo file. 18 18 - # 19 19 - # One thing that should be noted is the the ALL keyword is not 20 20 - # supported. There can be only one entry that matches a given 21 21 - # repository.