Re: Why are submodules not automatically handled by default or at least configurable to do so?
- From
Nazri Ramliy <ayiehere@gmail.com>
- Date
- Oct 26, 2015, 04:48 UTC
- Message-ID
- <CAEY4ZpPduXXqgW3rWn9rzkpHrTvY8QfPX=YcBZ_DpyVwnsZ6jw@mail.gmail.com>
- In-Reply-To
- <D4E5E890658.000004DCjohsmi9933@inbox.com>
On Mon, Oct 26, 2015 at 7:10 AM, John Smith <johsmi9933@inbox.com> wrote:
> When would people routinely check out a branch and want to stay with the submodules as > the have been checked out for the old branch?
I do this a lot. At my $dayjob we have a super project with bunch of sub projects. Each subproject has its corresponding rpm spec file in the superproject - it's quite often that I work on a "git-merge-base--octopus" branch that updates only the spec files and nothing else - so when changing between branches I don't care what states the submodules are in. When the fixes to the spec files are ready I just checkout to the respective branches and merge in the changes - I don't actively do "git submodule update" when switching to different branches.
nazri