- Besides the usual SCCS commands, several ``pseudo-commands'' can be
- issued. These are:
-
- e\bed\bdi\bit\bt Equivalent to ``get -e''.
-
- d\bde\bel\blg\bge\bet\bt Perform a delta on the named files and then get new versions.
- The new versions will have id keywords expanded, and will not
- be editable. The -\b-m\bm, -\b-p\bp, -\b-r\br, -\b-s\bs, and -\b-y\by flags will be passed
- to d\bde\bel\blt\bta\ba, and the -\b-b\bb,\b, -\b-c\bc, -\b-e\be, -\b-i\bi, -\b-k\bk, -\b-l\bl, -\b-s\bs,
- and -\b-x\bx flags will be passed to get.
-
- d\bde\bel\ble\bed\bdi\bit\bt Equivalent to d\bde\bel\blg\bge\bet\bt except that the g\bge\bet\bt phase includes the -\b-e\be
- flag. This option is useful for making a _\bc_\bh_\be_\bc_\bk_\bp_\bo_\bi_\bn_\bt of your
- current editing phase. The same flags will be passed to delta
- as described above, and all the flags listed for above except
- -\b-e\be and -\b-k\bk are passed to e\bed\bdi\bit\bt.
-
- c\bcr\bre\bea\bat\bte\be Creates an SCCS file , taking the initial contents from the
- file of the same name. Any flags to a\bad\bdm\bmi\bin\bn are accepted. If
- the creation is successful, the files are renamed with a comma
- on the front. These should be removed when you are convinced
- that the SCCS files have been created successfully.
-
- f\bfi\bix\bx Must be followed by a -\b-r\br flag. This command essentially re-
- moves the named delta, but leaves you with a copy of the delta
- with the changes that were in it. It is useful for fixing
- small compiler bugs, etc. Since it doesn't leave audit trails,
- it should be used carefully.
-
- c\bcl\ble\bea\ban\bn This routine removes everything from the current directory that
- can be recreated from SCCS files. It will not remove any files
- being edited. If the -\b-b\bb flag is given, branches are ignored in
- the determination of whether they are being edited; this is
- dangerous if you are keeping the branches in the same directo-
- ry.
-
- u\bun\bne\bed\bdi\bit\bt This is the opposite of an e\bed\bdi\bit\bt or a ``get -e''. It should be
- used with extreme caution, since any changes you made since the
- get will be irretrievably lost.
-
- i\bin\bnf\bfo\bo Gives a listing of all files being edited. If the -\b-b\bb flag is
- given, branches (i.e., SID's with two or fewer components) are
- ignored. If the -\b-u\bu flag is given (with an optional argument)
- then only files being edited by you (or the named user) are
- listed.
- c\bch\bhe\bec\bck\bk Like i\bin\bnf\bfo\bo except that nothing is printed if nothing is being
- edited, and a non-zero exit status is returned if anything is
- being edited. The intent is to have this included in an
- _\bi_\bn_\bs_\bt_\ba_\bl_\bl entry in a makefile to insure that everything is in-
- cluded into the SCCS file before a version is installed.
-
- t\bte\bel\bll\bl Gives a newline-separated list of the files being edited on the
- standard output. Takes the -\b-b\bb and -\b-u\bu flags like i\bin\bnf\bfo\bo and
- c\bch\bhe\bec\bck\bk.
-
- d\bdi\bif\bff\bfs\bs Gives a d\bdi\bif\bff\bf listing between the current version of the
- program(s) you have out for editing and the versions in SCCS
- format. The -\b-r\br, -\b-c\bc, -\b-i\bi, -\b-x\bx, and -\b-t\bt flags are passed to
- g\bge\bet\bt; the -\b-l\bl, -\b-s\bs, -\b-e\be, -\b-f\bf, -\b-h\bh, and -\b-b\bb options are passed to
- d\bdi\bif\bff\bf. The -\b-C\bC flag is passed to d\bdi\bif\bff\bf as -\b-c\bc.
-
- p\bpr\bri\bin\bnt\bt This command prints out verbose information about the named
- files.
-
- -\b-r\br Runs s\bsc\bcc\bcs\bs as the real user rather than as whatever effective
- user s\bsc\bcc\bcs\bs is ``set user id'' to.
-
- -\b-d\bd Specifies a root directory for the SCCS files. The default is
- the current directory. If environment variable PROJECT is set,
- it will be used to determine the -\b-d\bd flag.
-
- -\b-p\bp flag defines the pathname of the directory in which the SCCS
- files will be found; ``SCCS'' is the default. The -\b-p\bp flag
- differs from the -\b-d\bd flag in that the -\b-d\bd argument is prepended
- to the entire pathname and the -\b-p\bp argument is inserted before
- the final component of the pathname. For example, ``sccs -d/x
- -py get a/b'' will convert to ``get /x/a/y/s.b''. The intent
- here is to create aliases such as ``alias syssccs sccs -
- d/usr/src'' which will be used as ``syssccs get cmd/who.c''.
-
- Certain commands (such as a\bad\bdm\bmi\bin\bn) cannot be run ``set user id''
- by all users, since this would allow anyone to change the au-
- thorizations. These commands are always run as the real user.
+ Besides the usual SCCS commands, several ``pseudo-commands'' can be is-
+ sued. These are:
+
+ e\bed\bdi\bit\bt Equivalent to ``get -e''.
+
+ d\bde\bel\blg\bge\bet\bt Perform a delta on the named files and then get new versions.
+ The new versions will have id keywords expanded, and will not be
+ editable. The -\b-m\bm, -\b-p\bp, -\b-r\br, -\b-s\bs, and -\b-y\by flags will be passed to
+ d\bde\bel\blt\bta\ba, and the -\b-b\bb,\b, -\b-c\bc, -\b-e\be, -\b-i\bi, -\b-k\bk, -\b-l\bl, -\b-s\bs, and -\b-x\bx flags will be
+ passed to get.
+
+ d\bde\bel\ble\bed\bdi\bit\bt Equivalent to d\bde\bel\blg\bge\bet\bt except that the g\bge\bet\bt phase includes the -\b-e\be
+ flag. This option is useful for making a _\bc_\bh_\be_\bc_\bk_\bp_\bo_\bi_\bn_\bt of your
+ current editing phase. The same flags will be passed to delta
+ as described above, and all the flags listed for above except -\b-e\be
+ and -\b-k\bk are passed to e\bed\bdi\bit\bt.
+
+ c\bcr\bre\bea\bat\bte\be Creates an SCCS file , taking the initial contents from the file
+ of the same name. Any flags to a\bad\bdm\bmi\bin\bn are accepted. If the cre-
+ ation is successful, the files are renamed with a comma on the
+ front. These should be removed when you are convinced that the
+ SCCS files have been created successfully.
+
+ f\bfi\bix\bx Must be followed by a -\b-r\br flag. This command essentially removes
+ the named delta, but leaves you with a copy of the delta with
+ the changes that were in it. It is useful for fixing small com-
+ piler bugs, etc. Since it doesn't leave audit trails, it should
+ be used carefully.
+
+ c\bcl\ble\bea\ban\bn This routine removes everything from the current directory that
+ can be recreated from SCCS files. It will not remove any files
+ being edited. If the -\b-b\bb flag is given, branches are ignored in
+ the determination of whether they are being edited; this is dan-
+ gerous if you are keeping the branches in the same directory.
+
+ u\bun\bne\bed\bdi\bit\bt This is the opposite of an e\bed\bdi\bit\bt or a ``get -e''. It should be
+ used with extreme caution, since any changes you made since the
+ get will be irretrievably lost.
+
+ i\bin\bnf\bfo\bo Gives a listing of all files being edited. If the -\b-b\bb flag is
+ given, branches (i.e., SID's with two or fewer components) are
+ ignored. If the -\b-u\bu flag is given (with an optional argument)
+ then only files being edited by you (or the named user) are
+
+ listed.
+
+ c\bch\bhe\bec\bck\bk Like i\bin\bnf\bfo\bo except that nothing is printed if nothing is being
+ edited, and a non-zero exit status is returned if anything is
+ being edited. The intent is to have this included in an _\bi_\bn_\bs_\bt_\ba_\bl_\bl
+ entry in a makefile to insure that everything is included into
+ the SCCS file before a version is installed.
+
+ t\bte\bel\bll\bl Gives a newline-separated list of the files being edited on the
+ standard output. Takes the -\b-b\bb and -\b-u\bu flags like i\bin\bnf\bfo\bo and c\bch\bhe\bec\bck\bk.
+
+ d\bdi\bif\bff\bfs\bs Gives a d\bdi\bif\bff\bf listing between the current version of the pro-
+ gram(s) you have out for editing and the versions in SCCS for-
+ mat. The -\b-r\br, -\b-c\bc, -\b-i\bi, -\b-x\bx, and -\b-t\bt flags are passed to
+ g\bge\bet\bt; the -\b-l\bl, -\b-s\bs, -\b-e\be, -\b-f\bf, -\b-h\bh, and -\b-b\bb options are passed to
+ d\bdi\bif\bff\bf. The -\b-C\bC flag is passed to d\bdi\bif\bff\bf as -\b-c\bc.
+
+ p\bpr\bri\bin\bnt\bt This command prints out verbose information about the named
+ files.
+
+ -\b-r\br Runs s\bsc\bcc\bcs\bs as the real user rather than as whatever effective us-
+ er s\bsc\bcc\bcs\bs is ``set user id'' to.
+
+ -\b-d\bd Specifies a root directory for the SCCS files. The default is
+ the current directory. If environment variable PROJECT is set,
+ it will be used to determine the -\b-d\bd flag.
+
+ -\b-p\bp Defines the pathname of the directory in which the SCCS files
+ will be found; ``SCCS'' is the default. The -\b-p\bp flag differs
+ from the -\b-d\bd flag in that the -\b-d\bd argument is prepended to the en-
+ tire pathname and the -\b-p\bp argument is inserted before the final
+ component of the pathname. For example, ``sccs -d/x -py get
+ a/b'' will convert to ``get /x/a/y/s.b''. The intent here is to
+ create aliases such as ``alias syssccs sccs -d/usr/src'' which
+ will be used as ``syssccs get cmd/who.c''.
+
+ Certain commands (such as a\bad\bdm\bmi\bin\bn) cannot be run ``set user id''
+ by all users, since this would allow anyone to change the autho-
+ rizations. These commands are always run as the real user.
projects / unix-history / blobdiff