On Feb 15, 2013, at 1:57 PM, Thomas Ferris Nicolaisen wrote:

> If you want to single down to the diff on a single file, there is no first 
> class way to do this in Git. You could do a feature request to the Git 
> developer list, and argue that it belongs in git diff. I agree that it would 
> be useful, but not sure the developers will feel the same way.

Interesting. It is odd to me that you can say git diff commit1..commit2 -- 
myFile and that this usually works but suddenly stops working merely because 
myFile got renamed somewhere between commit and commit2. It feels like breakage 
and it surprises me that the developers don't feel it that way (but obviously 
they don't, or they would have done something about it).

> Some GUI tools support showing the history of a single file. You can then 
> select two revisions and do a compare between the two.
> 
> I guess you could script it by parsing the output of a git log with the two 
> revisions and the filename in one of them, finding the old file-name, and 
> then using it in a second diff call.

Thanks. I think that's just what I'll do! m.

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to