Re: [GSoC][PATCH v1] Disallow git commands from within unpopulated submodules

2017-04-06 Thread Prathamesh Chavan
> A couple of weeks back I floated a similar proposal of a patch[1], but > as far as I remember Peff hinted that it is a bad UI to do it on such a > generic early level[2]. And you also mention here that we'd not affect > git-diff or other commands that do not have RUN_SETUP set. > > [1] https://pu

Re: [GSoC][PATCH v1] Disallow git commands from within unpopulated submodules

2017-04-06 Thread Stefan Beller
On Wed, Apr 5, 2017 at 11:00 PM, Prathamesh Chavan wrote: > The main motivations for disallowing git commands within an > unpopulated submodule are: > > Whenever we run "git -C status" within an unpopulated submodule, it > falls back to the superproject. This occurs since there is no .git > file i

[GSoC][PATCH v1] Disallow git commands from within unpopulated submodules

2017-04-05 Thread Prathamesh Chavan
The main motivations for disallowing git commands within an unpopulated submodule are: Whenever we run "git -C status" within an unpopulated submodule, it falls back to the superproject. This occurs since there is no .git file in the submodule directory. So superproject's status gets displayed. Al

[GSoC][PATCH v1] Disallow git commands from within unpopulated submodules

2017-04-05 Thread Prathamesh Chavan
The main motivations for disallowing git commands within an unpopulated submodule are: Whenever we run "git -C status" within an unpopulated submodule, it falls back to the superproject. This occurs since there is no .git file in the submodule directory. So superproject's status gets displayed. Al