Hi! I've played around with git and found that 'git mv' does not honor what I tell it to do:
wiz@yt:~> mkdir a wiz@yt:~> cd a wiz@yt:~/a> git init . Initialized empty Git repository in /home/wiz/a/.git/ wiz@yt:~/a> touch a wiz@yt:~/a> git add a wiz@yt:~/a> git commit -m 'add a' [master (root-commit) 99d0ee7] add a 1 file changed, 0 insertions(+), 0 deletions(-) create mode 100644 a wiz@yt:~/a> git mv a b wiz@yt:~/a> touch Makefile wiz@yt:~/a> git add Makefile wiz@yt:~/a> git commit # Please enter the commit message for your changes. Lines starting # with '#' will be ignored, and an empty message aborts the commit. # On branch master # Changes to be committed: # renamed: a -> Makefile # new file: b # This is reproducible for me with "git version 2.3.0" on NetBSD-7.99.5/amd64. I guess this happens because the checksums of the files are the same and 'Makefile' is earlier when sorting, but since I explicitly told "git mv" old and new name, I think that's a bug nevertheless. Thomas -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
