Lines Matching refs:files

40 	Modules				list and descriptions of files
53 	trees with a baseline snapshot, to determine which files have
56 	size, ownership, ... for all files that filesync is managing
59 	The files and directory trees to be compared are determined 
61 	format (packingrules.4) permits files and or trees to be
63 	There are also provisions for filtering out unwanted files
64 	and for running programs to generate lists of files and
68 	spaces.  For names that appear in both trees, the files
70 	ownership and protections.  For files that are already
93 		files THE LAST TIME THEY WERE IN AGREEMENT.  If files
96 		files have never agreed, the baseline has no notions
106 		that describe which files (under those directories)
108 			files and or directories to be included
109 			wild cards for files or directories to be included
117 		the files that we are supposed to keep in sync, and
119 		of those files.  The structure of the tree mirrors
138 			a "file" tree, representing all files below the bases
151 			to add the file to a list of files requiring
165 		are believed to descibe files that have changed and require
176 		find out what files exist and stating all of
180 		files we don't want to evaluate (because we are
181 		limiting our attention to specific files and trees).
198 		which the files will be processed in pass III, and the
218 		data-structures for recording information about files
235 		routines to examine the in-core list of files and
237 		files are candidates for reconciliation).  This
238 		analysis includes figuring out which files should
251 		the status of all of the files that are described
253 	files.c
258 		files to be ignored, and to check file names against
265 		routines to examine a list of files that appear to
278 		information about files that is not readily available
317 			files.c
420 			listed files and directories should be evaluated
445 			is or do anything about it.  Such files are 
449 			files on the reconciliation list.  We do this