Thanks for the suggestions, I think I'll have everyone cloning the repositories to add the configuration settings in ~/.gitconfig instead.
On 07/09/2010, at 7:05 PM, David Aguilar wrote:
> On 9/7/10, Thomas Rast <trast@xxxxxxxxxxxxxxx> wrote:
>> Douglas Tan wrote:
>>>
>>> I have some config settings that I'll like to make default for
>>> anyone cloning/pulling from the central remote bare repository. I've
>>> tried to do this by editing the config file in the bare repository
>>> on the server but the change doesn't appear when cloning. How can I
>>> go about pushing default config settings to anyone cloing or pulling
>>> from the repository?
>>
>> You can't, since that would open a whole range of security issues.
>>
>> You can put some config defaults inside the repository itself, but it
>> is up to your users whether they apply them. Perhaps it's best to
>> write them as a shellscript that adds to the configuration file(s) so
>> that it is easy to apply it later, e.g.,
>>
>> #!/bin/sh
>> git config diff.jpg.textconv exiftool
>> cat >> .gitattributes <<EOF
>> *.jpg diff=jpg
>> EOF
>>
>> --
>> Thomas Rast
>> trast@{inf,student}.ethz.ch
>
> Also.. if you happen to have administrator access to their machines
> (or if they do) then you can roll an .rpm/.deb/etc. containing an
> /etc/gitconfig and install it on their machines. That'll apply these
> settings globally without them having to run a script everytime a repo
> is cloned.
> --
> David
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html