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

       bk export - export a patch or version of a BitKeeper repository

       bk export -tpatch [-hpST] [-s<alias>] [-i<pat>] [-x<pat>] -r<r1,r2>
       bk export -tplain [-kSTvw] [-s<alias>] [-i<pat>] [-x<pat>] -r<rev> <to>

       The  bk  export  command  generates a directory tree alongside the Bit-
       Keeper repository which contains checked-out copies of  all  the  files
       under  BitKeeper control.  It can also generate traditional (diff -Nur)
       patches between any two revisions of the source tree.  By  default,  bk
       export  only  exports  user files.  Files under the BitKeeper directory
       are not exported.  This behavior can be changed with the "-i" and  "-x"

       -h            Disable patch header.
       -i<pat>       Export only pathnames matching <pat> pattern (see below).
       -k            Do not expand keywords (default is to expand keywords).
       -p            Do procedural diffs when exporting a patch (see diff(1)).
       -r<rev>       Export the tree as of revision <rev>.
       --standalone  Just export the current component.  This has no effect in
                     a traditional standalone repository, but in a nested col-
                     lection, processes just the current component and not the
                     entire nested collection.
       -s<alias>     In a nested collection, export can recurse into  some  or
                     all  of  the  populated  components.  Using the -s<alias>
                     option limits the repositories processed to those  speci-
                     fied  by <alias>.  If this option is repeated the implied
                     subset is the union of all specified components.   If  no
                     <alias>  is  specified  that  is  taken to be the same as
       -T            Set gfile modification time to check-in time.
       -t<type>      Select export format via <type>:

                     plain       Export file in  plain  text  to  a  directory
                     patch       Export file in gnu patch format.
       -v            Be verbose.
       -w            Make files writable (default is read-only).
       -x<pat>       Export  all  pathnames  not  matching  <pat> pattern (see

       Include and/or exclude patterns may be used to control which files  are
       exported.   There may be multiple include and/or exclude patterns.  The
       patterns are a file glob the same as used by  bk  glob.   Patterns  are
       matched  against  the partial pathname from the root of the repository.
       If the partial pathname matches any of the exclude  patterns  then  the
       file  is  skipped.   If  there are one or more include patterns but the
       partial pathname does not match any of the include  patterns  then  the
       file is skipped.  Exclude processing takes precedence over include pro-

       When exporting patches there can be ambiguity as to which name is  used
       for  include/exclude  processing because some files may have been moved
       in the changes implied by the exported patch.  The include/exclude pro-
       cessing  always  applies  to any of file names contained in the changes
       implied by the patch.  For example, suppose you have  a  file  that  is
       currently  deleted  but  at the time of the patch was in src/foo.c.  If
       you told the system to export src/* then the file will be in the set.

       bk glob
       bk rset


BitKeeper Inc                         1E1                     bk export(7.3ce)