Oliver Kullmann, Mon, Jun 18, 2007 21:16:07 +0200: > 2. I issue "git mv file new_file". > > 3. Then I have to commit the renaming. I can't find anything on how > to do this (neither in the git-mv- nor in the git-commit-documentation). Just git-commit. git-mv is only so you don't have to run git add on the new file name and don't need to run "git-commit -a" afterwords. > So a hack is to use "git commit -a". Apparently this works. Even a plain "mv file new_file; git add new_file" would have worked. > 4. Now I have "new_file" in the repository, but without history > (except of the renaming operation), It does. Try "git log file new_file". After committing, that is > and I have still "file" in this history, but I can no longer get > access to the history of "file" via "gitk file" ? Well, you didn't commit the change yet. > This looks a bit strange to me (the renamed file has > no history, the old file still lurking around, but not > easily accessible). Git does not keep "renaming history". It does not have to, as it keeps how your project looked at each commit (point in history). - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
