| commit | 1cbd18300a8755ba46791b2aa6249fa537a1d651 | |
| author | Jens Lehmann <Jens.Lehmann@web.de> | |
| Tue, 7 Jan 2014 21:31:32 +0000 (7 22:31 +0100) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Tue, 7 Jan 2014 22:33:04 +0000 (7 14:33 -0800) | ||
| tree | fc770d1d8fbd67441ec085435995554187d54031 | treesnapshot (tar.gz zip) |
| parent | 932f7e47699993de0f6ad2af92be613994e40afe | commitdiff |
mv: better document side effects when moving a submodule
The "Submodules" section of the "git mv" documentation mentions what will
happen when a submodule with a gitfile gets moved with newer git. But it
doesn't talk about what happens when the user changes between commits
before and after the move, which does not update the work tree like using
the mv command did the first time.
Explain what happens and what the user has to do manually to fix that in
the new BUGS section. Also document this behavior in a new test.
Reported-by: George Papanikolaou <g3orge.app@gmail.com>
Signed-off-by: Jens Lehmann <Jens.Lehmann@web.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
The "Submodules" section of the "git mv" documentation mentions what will
happen when a submodule with a gitfile gets moved with newer git. But it
doesn't talk about what happens when the user changes between commits
before and after the move, which does not update the work tree like using
the mv command did the first time.
Explain what happens and what the user has to do manually to fix that in
the new BUGS section. Also document this behavior in a new test.
Reported-by: George Papanikolaou <g3orge.app@gmail.com>
Signed-off-by: Jens Lehmann <Jens.Lehmann@web.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| Documentation/git-mv.txt | diffblobblamehistory | |
| t/t7001-mv.sh | diffblobblamehistory |