3 .\" Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author]
4 .\" Generator: DocBook XSL Stylesheets v1.79.2 <http://docbook.sf.net/>
7 .\" Source: Git 2.46.0.46.g406f326d27
10 .TH "GIT\-REFS" "1" "2024-08-01" "Git 2\&.46\&.0\&.46\&.g406f326" "Git Manual"
11 .\" -----------------------------------------------------------------
12 .\" * Define some portability stuff
13 .\" -----------------------------------------------------------------
14 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
15 .\" http://bugs.debian.org/507673
16 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
17 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
20 .\" -----------------------------------------------------------------
21 .\" * set default formatting
22 .\" -----------------------------------------------------------------
23 .\" disable hyphenation
25 .\" disable justification (adjust text to left margin only)
27 .\" -----------------------------------------------------------------
28 .\" * MAIN CONTENT STARTS HERE *
29 .\" -----------------------------------------------------------------
31 git-refs \- Low\-level access to refs
35 \fIgit refs migrate\fR \-\-ref\-format=<format> [\-\-dry\-run]
39 This command provides low\-level access to refs\&.
44 Migrate ref store between different formats\&.
48 The following options are specific to \fIgit refs migrate\fR:
50 \-\-ref\-format=<format>
52 The ref format to migrate the ref store to\&. Can be one of:
63 for loose files with packed\-refs\&. This is the default\&.
75 for the reftable format\&. This format is experimental and its internals are subject to change\&.
81 Perform the migration, but do not modify the repository\&. The migrated refs will be written into a separate directory that can be inspected separately\&. The name of the directory will be reported on stdout\&. This can be used to double check that the migration works as expected before performing the actual migration\&.
83 .SH "KNOWN LIMITATIONS"
85 The ref format migration has several known limitations in its current form:
95 It is not possible to migrate repositories that have reflogs\&.
106 It is not possible to migrate repositories that have worktrees\&.
117 There is no way to block concurrent writes to the repository during an ongoing migration\&. Concurrent writes can lead to an inconsistent migrated state\&. Users are expected to block writes on a higher level\&. If your repository is registered for scheduled maintenance, it is recommended to unregister it first with git\-maintenance(1)\&.
120 These limitations may eventually be lifted\&.
123 Part of the \fBgit\fR(1) suite