git mv 命令 移动或重命名
2016-07-06 11:15
288 查看
最基本的代码:
手册:
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.
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.
git mv file_old file_new
手册:
NAME
git-mv - Move or rename a file, a directory, or a symlinkSYNOPSIS
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--forceForce 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.相关文章推荐
- Cobbler部署之FAQ处理
- C++基础7【难】 多态:实现原理 vptr指针 证明vptr存在 类的步长 纯虚函数:抽象类 案例 【面试题】
- Linux常用命令快捷键使用
- Gradle 如何使用Android Studio把自己的Android library分享到jCenter和Maven Central
- Junit4中的新断言assertThat的是用方法
- 让服务器iis支持.apk文件下载的设置方法
- opentsdb 分布式时间序列数据库安装实践
- javascript 数据类型
- 对快速排序的一些理解
- UILable &UIImageView& UIButton布局
- 如何使用IntelliJ IDEA 创建基于Maven构建的Web项目的过程
- 填报志愿(codevs 2930)
- Android简单涂鸦以及撤销、重做的实现方法
- 简单理解插入排序算法及Swift版的代码示例
- Jetty启动webApp报错,是因为没有加全依赖
- jquery选择器整理
- 【深入学习java集合框架】总篇章
- C++之类和对象课后习题简单实例
- Dreamweaver CS6 破解安装
- 堆——神奇的优先队列(上)