Re: [PATCH] Teach git submodule update to use distributed repositories

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Jul 17, 2008, 14:16 UTC
Message-ID: <alpine.DEB.1.00.0807171513560.8986@racer>
In-Reply-To: <320075ff0807170703l57fe26d2h1e9c4db1c38dd6f1@mail.gmail.com>

Hi,

On Thu, 17 Jul 2008, Nigel Magnay wrote:

Show 5 quoted lines

> Your attitude seems to be that the status-quo is in some way desirable; 
> "It's no wonder that this tool is awkward to use in your workflow.". 
> This workflow is really common, and there's actual, real people on this 
> list complaining about it. Don't we think it could be improved to be 
> non-awkward ?

I do not think that the status quo is the best possible.

But I think that the way you go makes things so confusing that those who use it apart from you will have problems.

For example, in your setup everybody would have to install _different_ remotes in every submodule.

And then some would ask themselves why the original origin was not good enough.

And others would specify "-o origin" all the time, thinking it was required.

There must be a better way to promote submodules to a usable state, Dscho