Re: [PATCH] Teach git submodule update to use distributed repositories
- From
Nigel Magnay <nigel.magnay@gmail.com>
- Date
- Jul 17, 2008, 12:21 UTC
- Message-ID
- <320075ff0807170521s26693381m60648468cce1c41c@mail.gmail.com>
- In-Reply-To
- <320075ff0807170520r200e546ejbad2ed103bd65f82@mail.gmail.com>
On Thu, Jul 17, 2008 at 1:13 PM, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
Show 9 quoted lines
> Hi, > > On Thu, 17 Jul 2008, Nigel Magnay wrote: > >> When doing a git submodule update, it fetches any missing submodule >> commits from the repository specified in .gitmodules. > > Huh? It takes what is in .git/config! Not what is in .gitmodules. >
Huh? And where does .git/config get it from? Oh, that's right, .gitmodules.
> So if you have another remote (or URL, e.g. if you have ssh:// access, but > the .gitmodules file lists git://), just edit .git/config. >
So for my usecase, you'd have me go in and change *evey single one* of my submodule refs from the centralised repository, *every time* I want to do a peer review?
Doesn't the current system strike you as being somewhat centralised in nature?
> I meant, that is the whole _point_ of having a two-step init/update > procedure. >
Are you just determined that submodules should remain useless for "the rest of us"?
> Ciao, > Dscho >