![]() How should this be fixed? Well, it kind of depends on what you want to see. Another problem with the initial window is that merge commits weren’t shown at all, so Commit D wasn’t included even though its contents were unique. Commit C came from Commit A, not Commit B. They’re chronologically adjacent but aren’t actually related to each other. The problem is the comparison between Commit B and Commit C. So, the diff history would look like this: Left Side The chronological order of the commits is A, B, C, D. In fact, that straightforward solution was the first version of the file history feature in Understand. So, combine the two into a diff view with forward and back buttons and you have a way to walk file history. Using “git log” to get the commits that touched a particular file is also straightforward. Getting a file diff from git is straightforward. “I want to walk through a file’s (git) history.” It sounds like a simple request. Abstract: Join me in a trip down the rabbit hole of making a “File History Diff Walker.”
0 Comments
Leave a Reply. |