Yoooooooo !! > I did read that discussion. My own situation was very much simpler, > since the ticket has no dependencies and the patch (if I may call it > that) only affected one file. I had also previously (4 months ago) > looked at the ticket when there was only one commit on it; now there > are 3. So I suppose one possibility is to look at all the commits > which are mention on that ticket and compare each with its parent. > For example > > git diff 94e3516^ 94e3516 > > shows me (I think) what changes were made by one of the commits. So > as long as I can find out which commits are relevant, I can do it. On > this ticket #8723 there are three commits and I just looked at each > one's diff from its predecessor, and I can see what the author did.
Oh. Then I guess Volker's command "git diff ^master" does the job. But it you allow me to insist, running "tig" would make it infinitely easier ! You can navigate and inspect each commit easily... Really really, it's a cool thing ! :-P Nathann -- You received this message because you are subscribed to the Google Groups "sage-git" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
