On Wed, 4 Sep 2013 11:39:21 -0700 (PDT) Ling <[email protected]> wrote:
> Thanks Konstantin, Yes I tried git log $newname $(git merge-base > $oldname $newname) and it works fine. That is not quite correct a call -- the proper one is git log $newname ^$basename or, expanded, git log $newname ^$(git merge-base $oldname $newname) Notice the "^" character in front of the second commit -- it's meaning is to exclude all commits reachable from the following revision specification from the set of commits defined by the first revision specification. See the "Specifying Ranges" section of the gitrevisions manual [1]. I, indeed, did not use "^" for the $basename argument in my previous e-mail to this thread (from which you seem to have finally copied the code), as I was in a hurry. My apologies for confusion. 1. https://www.kernel.org/pub/software/scm/git/docs/gitrevisions.html -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
