freshlybakedca.ke
Git fork
1git-mv(1)
2=========
3
4NAME
5----
6git-mv - Move or rename a file, a directory, or a symlink
7
8
9SYNOPSIS
10--------
11
12[synopsis]
13git mv [-v] [-f] [-n] [-k] <source> <destination>
14git mv [-v] [-f] [-n] [-k] <source>... <destination-directory>
15
16DESCRIPTION
17-----------
18Move or rename a file, directory, or symlink.
19
20In the first form, it renames _<source>_, which must exist and be either
21a file, symlink or directory, to _<destination>_.
22In the second form, _<destination-directory>_ has to be an existing
23directory; the given sources will be moved into this directory.
24
25The index is updated after successful completion, but the change must still be
26committed.
27
28OPTIONS
29-------
30`-f`::
31`--force`::
32 Force renaming or moving of a file even if the <destination> exists.
33`-k`::
34 Skip move or rename actions which would lead to an error
35 condition. An error happens when a source is neither existing nor
36 controlled by Git, or when it would overwrite an existing
37 file unless `-f` is given.
38`-n`::
39`--dry-run`::
40 Do nothing; only show what would happen
41
42`-v`::
43`--verbose`::
44 Report the names of files as they are moved.
45
46SUBMODULES
47----------
48Moving a submodule using a gitfile (which means they were cloned
49with a Git version 1.7.8 or newer) will update the gitfile and
50core.worktree setting to make the submodule work in the new location.
51It also will attempt to update the `submodule.<name>.path` setting in
52the linkgit:gitmodules[5] file and stage that file (unless `-n` is used).
53
54BUGS
55----
56Each time a superproject update moves a populated submodule (e.g. when
57switching between commits before and after the move) a stale submodule
58checkout will remain in the old location and an empty directory will
59appear in the new location. To populate the submodule again in the new
60location the user will have to run "git submodule update"
61afterwards. Removing the old directory is only safe when it uses a
62gitfile, as otherwise the history of the submodule will be deleted
63too. Both steps will be obsolete when recursive submodule update has
64been implemented.
65
66GIT
67---
68Part of the linkgit:git[1] suite