Documentation/git-fast-export.txt

   1 git-fast-export(1)
   2 ==================
   3
   4 NAME
   5 ----
   6 git-fast-export - Git data exporter
   7
   8
   9 SYNOPSIS
  10 --------
  11 'git fast-export [options]' | 'git fast-import'
  12
  13 DESCRIPTION
  14 -----------
  15 This program dumps the given revisions in a form suitable to be piped
  16 into linkgit:git-fast-import[1].
  17
  18 You can use it as a human readable bundle replacement (see
  19 linkgit:git-bundle[1]), or as a kind of an interactive
  20 linkgit:git-filter-branch[1].
  21
  22
  23 OPTIONS
  24 -------
  25 --progress=<n>::
  26         Insert 'progress' statements every <n> objects, to be shown by
  27         linkgit:git-fast-import[1] during import.
  28
  29 --signed-tags=(verbatim|warn|strip|abort)::
  30         Specify how to handle signed tags.  Since any transformation
  31         after the export can change the tag names (which can also happen
  32         when excluding revisions) the signatures will not match.
  33 +
  34 When asking to 'abort' (which is the default), this program will die
  35 when encountering a signed tag.  With 'strip', the tags will be made
  36 unsigned, with 'verbatim', they will be silently exported
  37 and with 'warn', they will be exported, but you will see a warning.
  38
  39 --export-marks=<file>::
  40         Dumps the internal marks table to <file> when complete.
  41         Marks are written one per line as `:markid SHA-1`. Only marks
  42         for revisions are dumped; marks for blobs are ignored.
  43         Backends can use this file to validate imports after they
  44         have been completed, or to save the marks table across
  45         incremental runs.  As <file> is only opened and truncated
  46         at completion, the same path can also be safely given to
  47         \--import-marks.
  48
  49 --import-marks=<file>::
  50         Before processing any input, load the marks specified in
  51         <file>.  The input file must exist, must be readable, and
  52         must use the same format as produced by \--export-marks.
  53 +
  54 Any commits that have already been marked will not be exported again.
  55 If the backend uses a similar \--import-marks file, this allows for
  56 incremental bidirectional exporting of the repository by keeping the
  57 marks the same across runs.
  58
  59
  60 EXAMPLES
  61 --------
  62
  63 -------------------------------------------------------------------
  64 $ git fast-export --all | (cd /empty/repository && git fast-import)
  65 -------------------------------------------------------------------
  66
  67 This will export the whole repository and import it into the existing
  68 empty repository.  Except for reencoding commits that are not in
  69 UTF-8, it would be a one-to-one mirror.
  70
  71 -----------------------------------------------------
  72 $ git fast-export master~5..master |
  73         sed "s|refs/heads/master|refs/heads/other|" |
  74         git fast-import
  75 -----------------------------------------------------
  76
  77 This makes a new branch called 'other' from 'master~5..master'
  78 (i.e. if 'master' has linear history, it will take the last 5 commits).
  79
  80 Note that this assumes that none of the blobs and commit messages
  81 referenced by that revision range contains the string
  82 'refs/heads/master'.
  83
  84
  85 Limitations
  86 -----------
  87
  88 Since linkgit:git-fast-import[1] cannot tag trees, you will not be
  89 able to export the linux-2.6.git repository completely, as it contains
  90 a tag referencing a tree instead of a commit.
  91
  92
  93 Author
  94 ------
  95 Written by Johannes E. Schindelin <johannes.schindelin@gmx.de>.
  96
  97 Documentation
  98 --------------
  99 Documentation by Johannes E. Schindelin <johannes.schindelin@gmx.de>.
 100
 101 GIT
 102 ---
 103 Part of the linkgit:git[1] suite