Skip site navigation (1)Skip section navigation (2)

FreeBSD Manual Pages


home | help
bk admin(7.3.3)		    BitKeeper User's Manual	       bk admin(7.3.3)

       bk admin	- administer BitKeeper files

       bk admin	options	[file ... | -]

       The  bk admin command is	used to	administer BitKeeper files.  There are
       options for changing per	file features, modifying file metadata,	 veri-
       fying  file  checksum and metadata, changing the	file compression mode,
       and/or recalculating the	file checksum.

       -C[id]	 set or	remove the changeset file  string  in  the  1.0	 delta
		 (very	rarely	used, not recommended).	 The string is used to
		 associate the file with a particular repository idea and usu-
		 ally the same as the output of	bk id.
       -D	 remove	 the  delta  changeset	marks (rarely used--not	recom-
       -fflag	 set a per file	flag.  Many of the flags may be	set  automati-
		 cally	upon  file  creation  by  adding  an entry to the Bit-
		 Keeper/etc/config file.  See bk help config-etc for  informa-
		 tion on how to	do so.	The possible values for	flag are:

		 BITKEEPER    mark  the	 file as a BitKeeper file (very	rarely
			      used, not	recommended)
		 EOLN_NATIVE  use the operating	 system's  native  end-of-line
			      termination (i.e., \r\n on Windows and \n	on all
			      other platforms.)	 EOLN_NATIVE is	set to "on" by
		 EOLN_UNIX    use  the UNIX end-of-line	termination (i.e., \n)
			      on all platforms.
		 EOLN_WINDOWS use the Windows end-of-line  termination	(i.e.,
			      \r\n) on all platforms.
		 EXPAND1      expand keywords in first line that contains key-
			      words only (printf conflicts)  (May  be  set  in
		 NOMERGE      do  not attempt to automerge this	file; treat it
			      as if it were a binary file and always  force  a
			      choice  between the local	and remote versions of
			      the file.
		 RCS	      expand RCS keywords, i.e., $keyword$ etc.	  (May
			      be set in	BitKeeper/etc/config).
		 SCCS	      expand  SCCS  keywords, i.e., %K%	etc.  (Setting
			      this in BitKeeper/etc/config applies this	behav-
			      ior  to  all subsequently	created	files; it does
			      not affect existing files! You must use bk admin
			      to explicitly on existing	files.)
       -Fflag	 delete	flag flag, reverting to	default	behavior.
       -h	 check	s.file	structure  in general, but limited to ATT SCCS
       -hh	 as above, but also check BitKeeper specific (in  addition  to
		 ATT SCCS) features.
       -hhh	 as above, but also check time stamps.
       -i[file]	 read initial text from	file (default stdin).
       -q	 run quietly.
       -ycomment make  comment	be the checkin comment for the initial checkin
		 (only valid with -i).
       -z	 recalculate file checksum.
       -Zalg	 compress stored  s.file  with	alg.   Compression  is	on  by
		 default  because  the space savings are substantial and there
		 is little or no performance difference.  The default  may  be
		 set in	BitKeeper/etc/config.  alg may be:

		 gzip	     like gzip(1)
		 none	     no	compression

       This  command  does way too much	and is likely to be split
       apart.  Do not depend on	these options for scripts.

       bk-check, bk-checksum, bk-chmod,	 bk-delta,  bk-cset,  bk-
       get, bk-id, bk-new, bk-log, bk-keywords,	bk-config-etc


BitKeeper Inc			      1E1		       bk admin(7.3.3)


Want to link to this manual page? Use this URL:

home | help