Re: Show containing branches in log?

From: Øyvind A. Holm <sunny@sunbase.org>
Date: Jul 3, 2014, 19:41 UTC
Message-ID: <CAA787rm=Pjy-GGzxCcy=NQNLUOCrTt4hYWS9iND8EAxxs67SuQ@mail.gmail.com>
In-Reply-To: <CAHd499A78BRVawWSHNnzJcD1Ca7RfFeEnJf0SB7py1MD5qwL0g@mail.gmail.com>

On 2 July 2014 16:50, Robert Dailey <rcdailey.lists@gmail.com> wrote:

Show 11 quoted lines

> I know that with the `git branch` command I can determine which
> branches contain a commit. Is there a way to represent this
> graphically with `git log`? Sometimes I just have a commit, and I need
> to find out what branch contains that commit. The reason why `git
> branch --contains` doesn't solve this problem for me is that it names
> almost all branches because of merge commits. Too much ancestry has
> been built since this commit, so there is no way to find the "closest"
> branch that contains that commit.
>
> Is there a way to graphically see what is the "nearest" named ref to
> the specified commit in the logs?

I have created a script for just this functionality which I use very often, and have created a gist with the files at <https://gist.github.com/sunny256/2eb583f21e0ffcfe994f>, I think it should solve your problem. It contains these files:

  git-wn

"wn" means "What's New" and will create a visual graph of all commits which has a specified ref as ancestor. It also needs the following script, just put it into your $PATH somewhere:

  git-lc

"lc" means "List branches Containing this commit" and generates a list of all branches containing a specified ref.

The files originates from <https://github.com/sunny256/utils>, but I've modified them in the gist to make your life easier. :)

Hope that helps, Øyvind