Re: [RFC/PATCH] add update to branch support for "floating submodules"
- From
Leif Gruenwoldt <leifer@gmail.com>
- Date
- Dec 12, 2011, 19:13 UTC
- Message-ID
- <CALFF=ZRB7qjj7VMhzr12ySdHmZsySoqceu5brFht8rX1+W3NPg@mail.gmail.com>
- In-Reply-To
- <4EE64B04.8080405@ursus.ath.cx>
On Mon, Dec 12, 2011 at 1:42 PM, Andreas T.Auer <andreas.t.auer_gtml_37453@ursus.ath.cx> wrote:
Show 16 quoted lines
> The next question is: Wouldn't you like to have the new stable branch only > pulled in, when the projectX (as the superproject) is currently on that new > development branch (maybe master)? > > But if you checkout that fixed released version 1.2.9.8, wouldn't it be > better that in that case the gitlinked version of the submodule is checked > out instead of some unrelated new version? I mean, when the gitlinks are > tracked with the projectX commits, this should work well. > > And what about a maintenance branch, which is not a fixed version but a > quite stable branch which should only have bugfixes. Shouldn't the auto-pull > be disabled in that case, too? > > I think the "auto-pull" behavior should depend on the currently checked out > branch. So the configuration options should allow the definition of one or > more mappings.
Yes. I think you nailed it. The floating behaviour would best be configured per branch.
An aside. Would this mean a "git pull" on the product repo would automatically do a pull (git submodule update) on the submodule too?