bk ignore(7.3ce)            BitKeeper User's Manual           bk ignore(7.3ce)

       bk ignore - ignore shell glob patterns

       bk ignore <glob> [<glob> ...]

       bk  ignore  tells  BitKeeper to ignore specified files when looking for
       extra files that are not under revision control.  This affects the out-
       put  of  bk  gfiles -x and all commands that use its output, such as bk
       citool and bk extras.

       Typical things to ignore are object files, core  files,  a.out,  *.exe,
       and the like.

       Patterns  that  do  not  contain  a  slash  (`/') character are matched
       against the basename of the  file;  patterns  containing  a  slash  are
       matched  against  the  pathname of the file relative to the root of the
       repository.  Using './' at the start of a  pattern  means  the  pattern
       applies only to the repository root.

       For  example,  if you always want to ignore files named JUNK regardless
       of which directory they are in, you can say

           bk ignore JUNK

       This matches JUNK and sub/dir/JUNK but not JUNK-PRECIOUS.

       If you want to match a file in just one subdirectory, you can do

           bk ignore sub/directory/this_one

       which matches sub/directory/this_one but not other_dir/this_one.

       If you want to ignore just the JUNK file at the root of the repository,
       you can do

           bk ignore ./JUNK

       which matches JUNK but not sub/dir/JUNK.

       You can also prune certain subdirectories of your repository by append-
       ing " -prune" to the  directory  path;  no  BitKeeper  operations  will
       descend into that directory.

           bk ignore 'sub/dir/build -prune'

       Note:  It's  important  to  use the quotes as shown when using "-prune"
       because each command argument is treated as a  separate  pattern.   You
       may  use  "-prune"  only  with directory paths that are relative to the
       root of the repository.

       Pruning large non-revision controlled directory trees  that  appear  in
       your repository can significantly improve performance in some cases.

       With no arguments, bk ignore shows the current ignore list.

       The  ignore  list  is stored in the file BitKeeper/etc/ignore.  You may
       edit this file if you wish; the format is simply  one  glob  per  line.
       Editing  the  ignore  file  is  the only way to remove entries from the

       The default ignore list is

           PENDING -prune
           BitKeeper/log -prune
           BitKeeper/tmp -prune
           BitKeeper/writer -prune
           BitKeeper/readers -prune

       The following additions are suggested:


       You may manually add additional ignore patterns on a  per  user  basis.
       For  example, if you have a tendency to have a file called "notes" that
       you never want to check in, and you also use .xxx as your  junk  files,
       then do this:

           $ echo notes >> "`bk dotbk`/ignore"
           $ echo '*.xxx' >> "`bk dotbk`/ignore"

       bk citool
       bk extras
       bk gfiles
       bk status


BitKeeper Inc                         1E1                     bk ignore(7.3ce)