Stefan Beller <sbel...@google.com> writes: > On Thu, Jul 13, 2017 at 8:59 AM, Jeff King <p...@peff.net> wrote: >>> This triggers two reactions for me: >>> >>> (a) We should totally do that. >> >>> (b) It's a rabbit hole to go down. >> >> And yes, I had both of those reactions, too. We've had the >> "project-level .gitconfig" discussion many times over the years. And it >> generally comes back to "you can ship a snippet of config and then give >> people a script which adds it to their repo". > > I see this "project-level .gitconfig" via the .gitmodules file. > See GITMODULES(5), anything except submodule.<name>.path is > just project-level .gitconfig,...
They were from day one meant as a suggestion made by the project. You do not have to follow them and you are free to update them, i.e. after "submodule init" copied URL to point at a closer mirror, for example.
