On Tue, Aug 19, 2014 at 03:23:36PM -0500, Robert Dailey wrote:
> On Tue, Aug 19, 2014 at 2:30 PM, Heiko Voigt <hvo...@hvoigt.net> wrote:
> > Well the remote for the submodule is currently only calculated once,
> > when you do the initial
> > git submodule update --init
> > that clones the submodule. Afterwards the fixed url is configured under
> > the name 'origin' in the submodule like in a normal git repository that
> > you have freshly cloned. Which remote is used for cloning depends on the
> > configured remote for the current branch or 'origin'.
> > When you do a fetch or push with --recurse-submodules it only executes a
> > 'git fetch' or 'git push' without any specific remote. For fetch the
> > same commandline options (but only the options) are passed on.
> > Here it might make sense to guess the remote in the submodule somehow
> > and not do what fetch without remotes would do.
> > For the triangular workflow not much work has been done in regards to
> > submodule support.
> > But since a submodule behaves like a normal git repository maybe there
> > is not much work needed and we can just point to the workflow without
> > submodules most times. We still have to figure that out properly.
> Maybe then the only thing we need is a --with-remote option for git
> submodule? ::
> git submodule update --init --with-remote myremote
> The --with-remote option would be a NOOP if it's already initialized,
> as you say. But I could create an alias for this as needed to make
> sure it is always specified.
I would actually error out when specified in already cloned state.
Because otherwise the user might expect the remote to be updated.
Since we are currently busy implementing recursive fetch and checkout I have
added that to our ideas list so we do not forget about it.
In the meantime you can either use the branch.<name>.remote
configuration to define a remote to use or just use 'origin'.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html