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 23, 2014, 17:00 UTC
Message-ID
<lo9mg1$bma$1@ger.gmane.org>
In-Reply-To
<53A6F978.4010005@web.de>
Jens Lehmann wrote:
> 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.

Such a menu entry might be useful, but it is still different workflow. It would be useful in the 'that commit sounds interesting - show me' case. I would need to see the commit title to know if it sounds interesting though.

Your suggestion involves a different window and context, but all I want to see is a list of commit titles so I can press 'up' to see the next ones, not have to close a window first before I can see the next list, and then have to right-click to see the list of commits.

Is it so difficult to list the titles of all of the newly-reachable commits? Even with a config option? Even an undocumented option?

Failing all of that, can you show me where the code would need to be changed to list all of the newly-reachable commits? I can keep a commit for myself then.

Thanks,
Steve.
Previous: Stephen KellyNext: Stephen Kelly
Message 7 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.