Re: gitk with submodules does not show new commits on other branches

From: Jens Lehmann <jens.lehmann@web.de>
Date: Jun 22, 2014, 15:42 UTC
Message-ID: <53A6F978.4010005@web.de>
In-Reply-To: <lo6o2h$vva$1@ger.gmane.org>

Am 22.06.2014 16:09, schrieb Stephen Kelly:

Show 23 quoted lines

> 
> Hello,
> 
> boost.git, is using submodules. 
> 
> If I run gitk after a pull, there are some messages along the lines of 
> 
> 
>     Update preprocessor from develop.
> 
>   Submodule libs/preprocessor 9d2d1ff..1422fce:
>     Merge branch 'master' into develop
> 
> 
> That is, it shows only the merge. 
> 
> If I then run 
> 
>  git log --oneline 9d2d1ff..1422fce 
> 
> I can see the commits which were made on master and then merged into 
> develop. Please show the same information (ie all commits newly reachable 
> from develop) in the submodule gitk output.

This should not happen by default. If you have a feature branch based workflow, the merge is just what you want to see. And "git submodule summary" is giving you the exact same information.

But I agree that this is suboptimal for your workflow. What about adding a "Visualize These Changes In The Submodule" menu entry for the context menu of a change in gitk just like the one git gui already has? Then the user could examine the merges in more detail if he wants.