Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

git-mv(1) [xfree86 man page]

GIT-MV(1)							    Git Manual								 GIT-MV(1)

NAME
       git-mv - Move or rename a file, a directory, or a symlink

SYNOPSIS
       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 gitmodules(5) file and stage that file (unless -n is used).

BUGS
       Each time a superproject update moves a populated submodule (e.g. when switching between commits before and after the move) a stale
       submodule checkout will remain in the old location and an empty directory will appear in the new location. To populate the submodule again
       in the new location the user will have to run "git submodule update" afterwards. Removing the old directory is only safe when it uses a
       gitfile, as otherwise the history of the submodule will be deleted too. Both steps will be obsolete when recursive submodule update has
       been implemented.

GIT
       Part of the git(1) suite

Git 2.17.1							    10/05/2018								 GIT-MV(1)

Check Out this Related Man Page

GITMODULES(5)							    Git Manual							     GITMODULES(5)

NAME
gitmodules - defining submodule properties SYNOPSIS
$GIT_WORK_DIR/.gitmodules DESCRIPTION
The .gitmodules file, located in the top-level directory of a git working tree, is a text file with a syntax matching the requirements of git-config(1). The file contains one subsection per submodule, and the subsection value is the name of the submodule. Each submodule section also contains the following required keys: submodule.<name>.path Defines the path, relative to the top-level directory of the git working tree, where the submodule is expected to be checked out. The path name must not end with a /. All submodule paths must be unique within the .gitmodules file. submodule.<name>.url Defines an url from where the submodule repository can be cloned. submodule.<name>.update Defines what to do when the submodule is updated by the superproject. If checkout (the default), the new commit specified in the superproject will be checked out in the submodule on a detached HEAD. If rebase, the current branch of the submodule will be rebased onto the commit specified in the superproject. If merge, the commit specified in the superproject will be merged into the current branch in the submodule. This config option is overridden if git submodule update is given the --merge or --rebase options. EXAMPLES
Consider the following .gitmodules file: [submodule "libfoo"] path = include/foo url = git://foo.com/git/lib.git [submodule "libbar"] path = include/bar url = git://bar.com/git/lib.git This defines two submodules, libfoo and libbar. These are expected to be checked out in the paths include/foo and include/bar, and for both submodules an url is specified which can be used for cloning the submodules. SEE ALSO
git-submodule(1) git-config(1) DOCUMENTATION
Documentation by Lars Hjemli <hjemli@gmail.com[1]> GIT
Part of the git(1) suite NOTES
1. hjemli@gmail.com mailto:hjemli@gmail.com Git 1.7.1 07/05/2010 GITMODULES(5)
Man Page

Featured Tech Videos