git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
SKStephen Kelly <steveire@gmail.com>
Date
Jun 22, 2014, 15:45 UTC
Message-ID
<lo6tnh$p3c$1@ger.gmane.org>
In-Reply-To
<53A6F978.4010005@web.de>
Jens Lehmann wrote:
> Am 22.06.2014 16:09, schrieb Stephen Kelly:
Show 5 quoted lines
>> 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.
In my case, it is not what I want to see :).
> 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?
Can you tell me how to find and try that out in git gui?
Thanks,
Steve.
Previous: Jens LehmannNext: Stephen Kelly
Message 3 of 11 in “gitk with submodules does not show new commits on other branches”
  1. Stephen KellyJun 22, 2014
  2. Jens LehmannJun 22, 2014
  3. Stephen KellyJun 22, 2014
  4. Stephen KellyJun 23, 2014
  5. Jens LehmannJun 23, 2014
  6. Stephen KellyJun 23, 2014
  7. Stephen KellyJun 23, 2014
  8. Stephen KellyJun 23, 2014
  9. Stephen KellyJun 23, 2014
  10. Jens LehmannJun 23, 2014
  11. Stephen KellyJun 24, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.