On Sun, 4 Feb 2007, Jeff King wrote: > > Just a thought, but it might be useful to blame the contents of an > arbitrary file (but starting the history at a given pathname). Something > like "git blame --contents /tmp/foo.c file.c", with contents defaulting > to "file.c". There's much discussion of editor interfaces, and this > leaves the possibility of git-blaming the contents of the editor buffer > (after writing it out to a temp file) without having to save changes to > the working tree file. I agree, that probably would make most sense. If we do this at all. On the other hand, I suspect that most editors would probably want to pipe the contents to the program, not write it to a temp-file. (I think it's a worthy feature, but Junio's patch wasn't exactly pretty, so the question boils down to whether it's really worth it). Linus - 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