Changeset 44 for confman/confman
- Timestamp:
- 03/29/2006 16:36:44 (6 years ago)
- File:
-
- 1 edited
-
confman/confman (modified) (14 diffs)
Legend:
- Unmodified
- Added
- Removed
-
confman/confman
r42 r44 90 90 91 91 Usage: 92 $MYNAME [ setup | s ]92 $MYNAME setup 93 93 94 94 The setup command is intended to be run the first time you use $MYNAME. … … 103 103 104 104 Usage: 105 $MYNAME [ create | cr ]module105 $MYNAME create module 106 106 107 107 The create command will cause a new module, named module, to appear as a … … 128 128 129 129 Usage: 130 $MYNAME [ update | u ]130 $MYNAME update 131 131 132 132 The update command will update your working copy of all the modules … … 211 211 212 212 The import subcommand adds the specified file to your working copy of the 213 repository. You should specify the absolute filename, relative to /.213 repository. 214 214 215 215 EOF … … 221 221 222 222 Usage: 223 $MYNAME [ remove | re | rm ] module file 224 225 The remove subcommand removes a file from version control under the listed 226 module. It will NOT remove the file from the live filesystem. It will 227 immediately commit the change to the repository. 223 $MYNAME rm file 224 225 The remove subcommand removes a file from version control It will NOT remove 226 the file from the live filesystem. 228 227 229 228 EOF … … 235 234 236 235 Usage: 237 $MYNAME mkdir module directory [ mode ] 238 239 This command will create a new version-controlled directory in module. 240 Specify the directory relative to the live file-systems root: 241 "/usr/local/etc". Parent directories do not have to exist; they will be 242 created automagically. This command only affects your working copy. It does 243 not commit the change. 236 $MYNAME mkdir directory 237 238 This command will create a new version-controlled directory in your working 239 copy. Parent directories do not have to exist; they will be created 240 automagically. This command only affects your working copy. It does not commit 241 the change. 244 242 245 243 EOF … … 265 263 266 264 Usage: 267 $MYNAME chown module [ file | directory ] owner268 269 The chown subcommand takes a directory and an owner relative to the system270 root and changes ownership.265 $MYNAME chown [ -R ] owner [ file | directory ] 266 267 The chown command works like it's unix equivalent. It does not support 268 user:group notation. The only option it will take is -R for recursive. 271 269 272 270 EOF … … 278 276 279 277 Usage: 280 $MYNAME chgrp module [ file | directory ] group281 282 The chgrp subcommand takes a directory and an group relative to the system283 root and changes ownership.278 $MYNAME chgrp group [ file | directory ] 279 280 The chgrp command works like it's unix equivalent. The only option it will take 281 is -R for recursive. 284 282 285 283 EOF … … 291 289 292 290 Usage: 293 $MYNAME chmod module [ file | directory ] mode 294 295 The chmod subcommand takes a directory and an mode relative to the system 296 root and changes ownership. 291 $MYNAME chmod mode [ file | directory ] 292 293 The chmod command works like it's unix equivalent. Note that it will only 294 accept octets as permissions -- it will not interpret symbolic permissions 295 correctly. The only option it will take is -R for recursive. 297 296 298 297 EOF … … 304 303 305 304 Usage: 306 $MYNAME chcom module [ file | directory ] comment-character305 $MYNAME chcom comment-character [ file | directory ] 307 306 308 307 The chcom subcommand takes a file or directory as an argument and changes the … … 318 317 319 318 Usage: 320 $MYNAME [ checklook | chlk | chls | checklist ]module319 $MYNAME checklook module 321 320 322 321 The checklook command peeks into the checkpoints for the specified module … … 332 331 333 332 Usage: 334 $MYNAME [ checknew | chnw ]module name333 $MYNAME checknew module name 335 334 336 335 The newcheck command creates a named checkpoint for the specified module. … … 345 344 346 345 Usage: 347 $MYNAME [ checkclear | chcl | chrm ]module name346 $MYNAME checkclear module name 348 347 349 348 The rmcheck command clears a named checkpoint from the specified module. … … 358 357 359 358 Usage: 360 $MYNAME [ rollback | ro ]module [ checkpoint | YYYYMMDD [HHMM] ]359 $MYNAME rollback module [ checkpoint | YYYYMMDD [HHMM] ] 361 360 362 361 The rollback command first rolls your working copy of module back to the
Note: See TracChangeset
for help on using the changeset viewer.
