Re: RFC: display dirty submodule working directory in git gui and gitk
- From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
- Date
- Jan 4, 2010, 17:51 UTC
- Message-ID
- <fcaeb9bf1001040951r3f797750o5ebd25e93c0272ea@mail.gmail.com>
- In-Reply-To
- <alpine.DEB.1.00.1001041038520.4985@pacific.mpi-cbg.de>
On 1/4/10, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
Show 12 quoted lines
> The real problem is that submodules in the current form are not very well > designed. For example, a submodule being at a different commit than in > the superproject's index is not as fatal as the submodule having changes. > > So in the long run, IMHO a proper redesign of the submodules would not > make only a little sense (it does not help, though, that those who > implemented and furthered the current approach over other discussed > approaches do not use submodules themselves -- not even now). > > In ths short run, we can paper over the shortcomings of the submodules by > introducing a command line option "--include-submodules" to > update-refresh, diff-files and diff-index, though.
Incidentally I was just drafting git-super.sh it see how far it goes. The goal was to implement some cross-module operations over time. "git super status", "git super commit" and others could be handy.
-- Duy