- Timestamp:
- Dec 25, 2007, 4:37:57 AM (15 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/readme.txt
r525 r526 39 39 ''other''. 40 40 41 From svndigest 0.7, it is possible to set the configuration file which42 rules are used for different files. For more on how to configure43 svndigest see below. If no configuration file is given or no rules are 44 given, a set of default rules are used. For files named `*.h`, for 45 example, rules allowing to detect comments as either `// ... \n` or 46 `/*... */`. These rules can be set in the configuration file using a41 From svndigest 0.7, it is possible to configure which rules are used 42 for different files. For more on how to configure svndigest see 43 below. If no configuration file is given or no rules are given, a set 44 of default rules are used. For files named `*.h`, for example, rules 45 allowing to detect comments as either `// ... \n` or `/* 46 ... */`. These rules can be set in the configuration file using a 47 47 one-liner like: 48 48 … … 59 59 can be found in directory `.svndigest`, and the svndigest screenshots 60 60 that can be reached through http://trac.thep.lu.se/svndigest/. 61 62 Sometimes it might be useful if a file could be parsed as though it 63 was going under a different name. It could, for example, be useful if 64 files named `Makefile.in` could be parsed as `Makefile` or files named 65 `test_repo.sh.in` could be parsed as though it was named 66 `test_repo.sh`. More generally, it would be useful if files named 67 `<file-name-pattern>.in` could be parsed as though it was named 68 `<file-name-pattern>`. For this reason it is possible to set rules on 69 how a filename should be interpreted (see section 70 [file-name-dictionary] in configuration file). Default behaviour is 71 that there is only one such a rule in use, namely the one described 72 above that trailing `.in` in file names are discarded. 73 61 74 62 75 == Different file types ==
Note: See TracChangeset
for help on using the changeset viewer.