From: Jens Lehmann Date: Mon, 26 Oct 2015 16:52:01 GMT Subject: Re: [RFC] URL rewrite in .gitmodules Message-ID: <562E5A31.7050903@web.de> In-Reply-To: Am 26.10.2015 um 17:34 schrieb Stefan Beller: > On Sun, Oct 25, 2015 at 8:12 AM, Lars Schneider wrote: >> On 20 Oct 2015, at 19:33, Junio C Hamano wrote: >>> I do not think this topic is specific to use of submodules. If you >>> want to encourage your engineers to fetch from nearby mirrors you >>> maintain, you would want a forest of url.mine.insteadof=theirs for >>> the external repositories that matter to you specified by >>> everybody's $HOME/.gitconfig, and one way to do so would be to have >>> them use the configuration inclusion. An item in your engineer >>> orientation material could tell them to add >>> >>> [include] >>> path = /usr/local/etc/git/mycompany.urlrewrite >>> >>> when they set up their "[user] name/email" in there. >>> >>> And you can update /usr/local/etc/git/mycompany.urlrewrite as >>> needed. >> Oh nice, I didn't know about "include". However, as mentioned to Stefan in this thread, I fear that our engineers will miss that. I would prefer a solution that does not need any additional setup. Therefore the suggestion to add rewrites in the .gitmodules file. > > How do you distribute new copies of Git to your engineers? > Maybe you could ship them a version which has the "include" line > already builtin as default? So your distributed copy of Git > would not just check the default places for configs, but also > some complied in /net/share/mycompany.gitconfig Which is just what we do at $DAYJOB, that way you can easily distribute all kinds of settings, customizations and hooks company-wide.