Thanks. This is actually does provide some value. The downside is if I 
merge to my build branch or my dev branches from master (production code) 
it brings all those commit with it that are already in prod but unrelated 
to the work so it is messy.
I need to parse that in some way so I only have the relevant merges for the 
current development and builds. Thanks for a pointer on this

On Tuesday, April 12, 2016 at 10:30:25 AM UTC-4, Dale R. Worley wrote:
> Kevin Wholley < <javascript:>> writes: 
> > I would like to see a history of any branch that merges into another 
> > branch. For example I have master as my production code. I also have a 
> > build branch and several development branches. When a development branch 
> is 
> > ready to build we merge into our build branch. At this point this 
> command 
> > is fine "git branch --merged" however, when the development branch 
> changes 
> > and the commit point moves this command does not list the branch(s) that 
> > merged to the build branch. I need to know all the changes merged in 
> from 
> > the dev branches to the build branch regardless if the commit point 
> > changes, kind of like a full history of the build branch. Is this 
> possible? 
> > How is it done? 
> If I understand you correctly, I think "git log --graph <branch name>" 
> will show you the history of the chosen branch with all merges going 
> into it.  What it doesn't do is label which ancestory commits are "part 
> of which branches".  In Git, that isn't a well-defined concept; commits 
> exist in a directed acyclic graph, and branches are pointers to 
> commits.  So the commit "my-branch^" doesn't *belong* to my-branch, 
> though in fact that commit may be reachable only from the commit 
> my-branch. 
> (Though it would help if "git log --graph" would label commits that are 
> branch heads.) 
> Dale 

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 
For more options, visit

Reply via email to