If you're confident the history's simple, you needn't bother. git can be directed to search more carefully for such things, at the expense of speed. renames and copies), see VonC's excellent comment. If your file may not have a simple history (e.g. (The checkout command first reads the file into the index, then copies it into the work tree, so there's no need to use git add to add it to the index in preparation for committing.) Now, all you have to do is this: # get the version of the file from the given commit You can also do this once you've started gitk through the view menu one of the options for a view is a list of paths to include.Įither way, you'll be able to find the SHA1 (hash) of the commit with the version of the file you want. Or, if you prefer the graphical view of gitk gitk path/to/file If your commit messages aren't good enough, and you need to see what was done to the file in each commit, use the -p/-patch option: git log -p path/to/file You can see the commits which have made modifications to given file(s) very easily: git log path/to/file
So let's start with finding the right commit. (We can't just muck around with history, because we've already pushed this content, and editing history messes with everyone else.) Once we know that, we'll need to make a new commit reverting the file to that state. So, we have to know which commit has the version of the file we want. It just tracks content - a commit is essentially a snapshot of the work tree, along with some metadata (e.g. First of all, git doesn't keep version numbers for individual files. We've made some number of commits, five of which changed a given file, and we want to revert the file to one of the previous versions. Let's start with a qualitative description of what we want to do (much of this is said in Ben Straub's answer).
0 kommentar(er)
