Re: Possible regression in master? (submodules without a "master" branch)
- From
W. Trevor King <wking@tremily.us>
- Date
- Mar 28, 2014, 02:33 UTC
- Message-ID
- <20140328023339.GC25485@odin.tremily.us>
- In-Reply-To
- <5334AC59.7010605@web.de>
On Thu, Mar 27, 2014 at 11:55:21PM +0100, Jens Lehmann wrote:
Show 5 quoted lines
> Me thinks that when a superproject doesn't have 'branch' configured > and does set 'update' to something other than 'checkout' for a > submodule it should better make sure 'master' is a valid branch in > there. Everything else sounds like a misconfiguration on the > superproject's part that warrants an error.
submodule.<name>.branch should only matter for --remote updates (and the initial clone, which is a special case of remote update). So having an alternative update mode and no submodule.<name>.branch *is* a valid configuration. It says:
* I want to integrate local submodule commits with superproject gitlink changes using the submodule.<name>.update strategy. * I never use --remote updates, so I haven't bothered to setup submodule.<name>.branch.
I can imagine folks using a workflow like that. And I think erroring out if they *do* try a --remote update shouldn't be too surprising for them.
Cheers, Trevor
-- This email may be signed or encrypted with GnuPG (http://www.gnupg.org). For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy