On Thu, Feb 14, 2013 at 8:02 PM, Matt Neuburg mattne...@gmail.com wrote:
My files have all been renamed, so to diff one of them to an earlier
commit I'm saying this sort of thing:
git diff HEAD:newname cb3e0a5fa8:oldname
I have to keep a list of the new names and old names beside me at
On Feb 15, 2013, at 7:48 AM, Bob Hiestand bob.hiest...@gmail.com wrote:
On Thu, Feb 14, 2013 at 8:02 PM, Matt Neuburg mattne...@gmail.com wrote:
My files have all been renamed, so to diff one of them to an earlier commit
I'm saying this sort of thing:
git diff HEAD:newname
On Fri, Feb 15, 2013 at 10:31 AM, Matt Neuburg mattne...@gmail.com wrote:
Have you tried the '-M' option to diff?
Yes, have you? It seems to have no effect when you supply an explicit
filename - presumably *because* you are supplying an explicit filename.
That's exactly my point.
I have;
On Feb 15, 2013, at 9:24 AM, Bob Hiestand bob.hiest...@gmail.com wrote:
your post didn't restrict the use to only filtering by path
It did; it showed an example of what I'm having to do, where I'm explicitly
comparing HEAD:newfile with oldCommit:oldfile. That is what I need to do:
compare a
On Friday, February 15, 2013 9:04:25 PM UTC+1, Matt Neuburg wrote:
On Feb 15, 2013, at 9:24 AM, Bob Hiestand bob.hi...@gmail.comjavascript:
wrote:
your post didn't restrict the use to only filtering by path
It did; it showed an example of what I'm having to do, where I'm
explicitly
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
My files have all been renamed, so to diff one of them to an earlier commit
I'm saying this sort of thing:
git diff HEAD:newname cb3e0a5fa8:oldname
I have to keep a list of the new names and old names beside me at all
times. This seems nuts. Is there a better way? Clearly git can tell from
