{"thread":{"id":"10177","subject":"Repository specific config file","startedAt":"2007-10-07T08:37:07Z","lastAt":"2007-10-07T16:06:37Z","messageCount":2,"participants":["Pekka Riikonen","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"55041","messageId":"Pine.NEB.4.64.0710070956340.12867@otaku.Xtrmntr.org","threadId":"10177","inReplyTo":null,"subject":"Repository specific config file","fromName":"Pekka Riikonen","fromEmail":"priikone@iki.fi","sentAt":"2007-10-07T08:37:07Z","receivedAt":"2007-10-07T08:37:07Z","isPatch":false,"sender":{"key":"priikone@iki.fi","avatar":null},"body":"Hello,\n\nHas there been any discussion or considerations adding a repository \nspecific config file that would be delivered to all cloned repositories \nautomatically?  This would allow the publisher of the repository to set up \nsome default settings to all developers cloning the repository.  This \ncould be useful to set up things like default aliases to ease up the work, \nto set that all remote branches are tracked, to list the configurations of \nsubmodules (so that people don't have to run submodule init), etc.\n\nUser should still be able to add configurations that overlap with the \nremote configuration and user should be able to ignore everything that \ncame from the parent.  Using ~/.gitconfig and /etc/gitconfig doesn't \nalways work well when the developers don't have access to the remote \nmachine (other than to clone the repository).  Maybe the simplest solution \nwould be to just add .gitconfig to the repository itself.\n\n \tPekka\n________________________________________________________________________\n  Pekka Riikonen                                 priikone at silcnet.org\n  Secure Internet Live Conferencing (SILC)       http://silcnet.org/\n"},{"id":"55056","messageId":"Pine.LNX.4.64.0710071704550.4174@racer.site","threadId":"10177","inReplyTo":"Pine.NEB.4.64.0710070956340.12867@otaku.Xtrmntr.org","subject":"Re: Repository specific config file","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-10-07T16:06:37Z","receivedAt":"2007-10-07T16:06:37Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Sun, 7 Oct 2007, Pekka Riikonen wrote:\n\n> Has there been any discussion or considerations adding a repository \n> specific config file that would be delivered to all cloned repositories \n> automatically? This would allow the publisher of the repository to set \n> up some default settings to all developers cloning the repository.\n\nSure!  Just check in the file \"gitconfig\" and tell the good users that \nthey can append it to their config with \"cat gitconfig >> .git/config\".\n\nOr have a script \"gitconfig.sh\" containing calls to \"git config\" which the \nusers can execute.\n\nBut you should not _force_ people to have a certain config.  It's their \nchoice.\n\nCiao,\nDscho\n"}]}