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

Jens Lehmann wrote: > Am 23.06.2014 20:24, schrieb Stephen Kelly: >> Stephen Kelly wrote: >> >>> I see that gitk is showing the output of git diff --submodule, similar >>> to git submodule summary. > > Right, and for your use case --submodule would have to learn a > different value in addition t

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

Am 23.06.2014 20:24, schrieb Stephen Kelly: > Stephen Kelly wrote: > >> I see that gitk is showing the output of git diff --submodule, similar to >> git submodule summary. Right, and for your use case --submodule would have to learn a different value in addition to 'log' and 'short'. And the defa

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

Stephen Kelly wrote: > I see that gitk is showing the output of git diff --submodule, similar to > git submodule summary. > > Assuming that is not going to be changed, maybe I can hack > parseblobdiffline locally. I have not really tried to read of write tcl > code before though, so I'd still pre

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

Stephen Kelly wrote: > 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. I see that gitk is showing the output of git diff --submodule, similar to git submodule summary. Assuming that

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

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 w

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

Jens Lehmann wrote: > Am 22.06.2014 17:45, schrieb Stephen Kelly: >> Jens Lehmann wrote: >> >>> Am 22.06.2014 16:09, schrieb Stephen Kelly: >>> 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 >>>

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

Am 22.06.2014 17:45, schrieb Stephen Kelly: > Jens Lehmann wrote: > >> Am 22.06.2014 16:09, schrieb Stephen Kelly: >> 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

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

Stephen Kelly 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? > > Can you tell me how to find and try that out in git gu

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

Jens Lehmann wrote: > Am 22.06.2014 16:09, schrieb Stephen Kelly: >> 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 wa

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

Am 22.06.2014 16:09, schrieb Stephen Kelly: > > 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' i

gitk with submodules does not show new commits on other branches

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 g