Re: git submodule update --merge
- From
Avery Pennarun <apenwarr@gmail.com>
- Date
- May 25, 2009, 19:04 UTC
- Message-ID
- <32541b130905251204q20b5600fr4486390cc9157f66@mail.gmail.com>
- In-Reply-To
- <alpine.DEB.1.00.0905252053070.4288@intel-tinevez-2-302>
On Mon, May 25, 2009 at 2:57 PM, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
Show 14 quoted lines
> Because in the project I use submodules most heavily, there is one > recurring theme: you cannot push to the submodules. And by "you" I mean > "a regular user". > > So virtually all you do in these submodules cannot be pushed at all. It > has to be submitted to the respective submodule maintainer. > > And guess what happens in such a case when you set that tentative "update" > variable to "merge"? > > Exactly. > > FWIW I consider any scenario where the average users have push access to > the submodule a toy scenario.
I have the same problem. Out of curiosity, how do you handle the case where you really need to make a change to the submodule and let your team members see that change, even though the submodule's upstream is slow and/or doesn't accept the patch?
In that situation, we've had to make local shared mirrors of all the submodules and point .gitmodules at that. But that would be your "toy" scenario - our local users have push access to the submodule.
Thanks,
Avery