Is it possible to merge renames in git if changes occur in a future commit than the rename? -
i have bit of odd issue repo. have branch dev, called other, , merged master refactors involved renaming bunch of files.
[other] /->[normal commits]-----------------\ / \ [master] (old)->(old)->---------->[potential file changes]--->[potentially difficultmerge due potential file changes] / [otherbranch] [massive rename]/ can change contents in later commit (actually java package identification) before merging other without having nasty resolution of these renames? files in question modified in other quite bit.
edit: git-merge recursive , patience should able pick merge nicely if it's not renamed, same logic apply renames?
why don't revert 'rename' merge, merge 'other' , merge 'rename' again? not perfect solution should work right here , right now.
take here figure out how correctly revert merge undo git merge hasn't been pushed yet
Comments
Post a Comment