On Sun, Dec 02, 2007 at 06:19:23PM -0800, Junio C Hamano wrote: > I think it is rather a sloppy error checking than a bug. It should be > throwing a stone back at you when you feed it a full path, or converting > it back to work tree relative path before using. I think it's not the only place. Doing "git diff /path/to/repo/file" silently produces an empty diff, even if there are changes in the file. -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
