On Tue, Feb 16, 2016 at 12:24:42PM -0800, Brian Norris wrote: > I'm not sure if this is a known behavior or a new bug report. I at least > couldn't find anyone mentioning this exact problem. > > I'm using a git repository that has multiple "inital commits" (i.e., a > few different directory trees were imported via svn-to-git as different > branches) whose histories have been merged together to the single master > branch, and the file I want to track is both added and removed in only > one of those lineages. When I try to do: > > $ git log -- <file> > > on the deleted file in the master branch, I get no history. But if I > checkout the particular sub-tree of the merge history, then git-log > returns the appropriate history. See the section on History Simplification in git-log. But basically, when you specify a pathspec, git does not traverse side branches that had no effect on the given pathspec. So imagine we are walking backwards through history and showing each commit, and we hit a merge where the content at that path is at some sha1 X. We see on one side of the merge that the parent was also at X, and on the other it was at Y. We do not bother following the commits down the second parent at all. Perhaps it touched the file and perhaps it did not, but it does not matter, as the merge threw away anything it did in favor of the first parent. Yours is a special case where the final result is "deleted". So there is a merge where one side had already deleted it, and the other side had some content, but the merge chose the deletion. If you want to see the full history, you can with "--full-history" (there are some other simplification possibilities, but I don't think any of them are interesting for your particular case). If you want to find the merge in question, something like: git log --graph --full-history -m --oneline --raw -- init/iptables.conf would work. In your case, it's probably: 8f4314b Move 'src/platform/init' to 'src/platform2' -Peff -- 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