Dan Zwell <dzwell@xxxxxxxxx> writes: > ... It is the same after I commit the new changes--at that point, > "git-diff-tree HEAD^ HEAD -p" spits out a nice patch, but "git-diff > HEAD^ HEAD" gives nothing. This part is most interesting. They are both about comparing two commits and do not interact with anything in the work tree nor your index. > I have tried git versions 1.5.1.6-1.5.3.3, and they all act the same, Do you mean 1.5.1.5 was Ok? Can you bisect it? > so I think the repository is corrupt. Does sound familiar to anybody? Not to me; and I do not think repository is corrupt from the two "HEAD^ vs HEAD" diff. There is something entirely different going on. > ... I can > restore from a recent backup and redo some changes, but I would like > to help troubleshoot this behavior if it is a git bug. Thanks. - 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
