At some point in our past branches of development in git were merged. However, the wrong merge decision was made and therefore some code didn\'t make it into master branch tha
If you know a line in a file that was modified by the git branch merge, you can do 'git blame file.txt' and determine the commit hash number and commit author of the line in the file. Then you can go through the git log and pull up the exact commit associated with the bad branch merge.
EDIT: In response to the author's comments, if you're looking for the disappearance of a certain line then 'git diff' combined with grep and binary search could be what you want. let's say you have commit numbers 0,1,2,3,4,5,6. You know that the line existed in revision 0, but disappeared in revision 6. Use 'git diff' plus grep to search for the disappearance.
git diff 0 6 | grep '- line I care about'
The first iteration, you'll see the line you care about disappearing. Then you cut the revision number in half and try again
git diff 0 3 | grep '- line I care about'
If the grep still shows the line disappearing ( with the '-' sign), then you know that the line disappeared in revision 0 to 3. If the grep doesn't show the line disappearing, then the line disappeared in revisions 4-6.
Keep cutting the revisions in half until you find the culprit.