summaryrefslogtreecommitdiff
path: root/Documentation/git-mv.txt
blob: b1f79881efdd181cf996672bc47c7772f21df8fd (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
git-mv(1)
=========
 
NAME
----
git-mv - Move or rename a file, a directory, or a symlink
 
 
SYNOPSIS
--------
[verse]
'git mv' <options>... <args>...
 
DESCRIPTION
-----------
Move or rename a file, directory or symlink.
 
 git mv [-v] [-f] [-n] [-k] <source> <destination>
 git mv [-v] [-f] [-n] [-k] <source> ... <destination directory>
 
In the first form, it renames <source>, which must exist and be either
a file, symlink or directory, to <destination>.
In the second form, the last argument has to be an existing
directory; the given sources will be moved into this directory.
 
The index is updated after successful completion, but the change must still be
committed.
 
OPTIONS
-------
-f::
--force::
	Force renaming or moving of a file even if the target exists
-k::
        Skip move or rename actions which would lead to an error
	condition. An error happens when a source is neither existing nor
	controlled by Git, or when it would overwrite an existing
        file unless '-f' is given.
-n::
--dry-run::
	Do nothing; only show what would happen
 
-v::
--verbose::
	Report the names of files as they are moved.
 
SUBMODULES
----------
Moving a submodule using a gitfile (which means they were cloned
with a Git version 1.7.8 or newer) will update the gitfile and
core.worktree setting to make the submodule work in the new location.
It also will attempt to update the submodule.<name>.path setting in
the linkgit:gitmodules[5] file and stage that file (unless -n is used).
 
GIT
---
Part of the linkgit:git[1] suite