The author of the commit refactored duplicated code by introducing a single helper function or The block of code did not exist in the file, but five identical copies of it existed in different files, all of which disappeared after the commit.The author of the commit was the inventor of that cool feature you were hunting its origin for (or the guilty party who introduced the bug) or The commit truly introduced the block of code.You may find that it is one of the many possible situations, including: When you find that before the commit the block of code did not exist in the file, you inspect the commit deeper.
Then you inspect the change of the commit to see if the block of code you are interested in is modified by it, as a commit that changes the file may not touch the block of code you are interested in, but only some other parts of the file. You'd start from the current block of code in a file, go back in the history to find the commit that changed the file. In the message, Linus outlined how an ideal content tracking system may let you find how a block of code came into the current shape. I found it referenced by this blog post, which could also be useful for you to find a viable solution: What matters is finding "where did this come from", and the gitĪrchitecture does that very well indeed - much better than anything else They aren't what you were interested in anyway. …I'm claiming that any SCM that tries to track renames is fundamentallyīroken unless it does so for internal reasons (ie to allow efficientĭeltas), exactly because renames do not matter.
#SWINSIAN RENAME PODCAST FILES HOW TO#
Even though I can give you no answer, I believe you can read this email Linus wrote back in 2005, it is very pertinent and might give you a hint about how to handle the problem: I have exactly the same issue that you are facing. How do the hardcore Git users get the history of a file when it was renamed? What is the 'real' way to do this? follow is a total hack, meant to just satisfy ex-SVN users who never On the command line, I can see the whole log across renames.Īccording to Linus Torvalds ( alternative link) the -follow switch is a "SVN noob" pleaser serious Git users don't use it:
I noticed that most of the graphical Git front-ends and IDE plugins don't seem to be able to display the history of a file if the file has been renamed.
0 kommentar(er)
