On Fri, Aug 30, 2013 at 09:51:25PM +0000, Justin Whear wrote:
> On Fri, 30 Aug 2013 14:35:04 -0700, H. S. Teoh wrote:
> 
> > On Fri, Aug 30, 2013 at 12:43:44PM -0700, Walter Bright wrote:
> > One of these days I'll have to research a little more how to more
> > easily identify the merge commit that pulled in a particular commit.
> > Since all commits only refer to their ancestors, git has no easy way
> > of following the chain downstream to the merge point (at least, none
> > that I know of).  If anyone knows some git-fu to do this, I'd be
> > very much obliged. :)
> > 
> > 
> > T
> 
> I think you can find the merge which introduced the commit with something like this:
> 
> git log <commit hash>..master --merges --ancestry-path
> 
> Though that includes subsequent merges; I think you just want the last one.

Cool, that did the trick! Yeah I just want the last one... but at least it's there. It's easy to ignore the rest. :)


T

-- 
The diminished 7th chord is the most flexible and fear-instilling chord. Use it often, use it unsparingly, to subdue your listeners into submission!