Skip to content
Snippets Groups Projects
Select Git revision
  • trunk
  • RELEASE_6_5_DRIVEDB
  • RELEASE_6_6_DRIVEDB
  • RELEASE_7_0_DRIVEDB
  • RELEASE_7_2_DRIVEDB
  • RELEASE_7_3_DRIVEDB
  • RELEASE_6_0_DRIVEDB
  • RELEASE_6_1_DRIVEDB
  • RELEASE_6_2_DRIVEDB
  • RELEASE_6_3_DRIVEDB
  • RELEASE_6_4_DRIVEDB
  • tags/RELEASE_7_4
  • tags/RELEASE_7_3
  • RELEASE_5_41_DRIVEDB
  • RELEASE_5_42_DRIVEDB
  • RELEASE_5_43_DRIVEDB
  • tags/RELEASE_7_2
  • tags/RELEASE_7_1
  • tags/RELEASE_7_0
  • RELEASE_5_40_DRIVEDB
20 results

modules

Blame
  • modules 1.12 KiB
    # 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.