# Maintaining commit.template config through clones

4 messages from 2008-04-17 to 2008-04-22. Participants: Toby Corkindale, Johannes Sixt.
Thread: https://gitlist.dev/t/13149

## Toby Corkindale, 2008-04-17 08:47

Subject: Maintaining commit.template config through clones
Message-ID: <48070EA4.2050503@rea-group.com>
URL: https://gitlist.dev/e/48070EA4.2050503%40rea-group.com

```
Hi,
I'm attempting to implement Git at our company, and we currently use a 
commit template for CVS. I can convert this to a Git-formatted template, 
and set it for use with git-config commit.template ....

However, once the repository is cloned, this configuration option 
vanishes from .git/config

Is there a way to make configuration options sticky?

thanks,
Toby

-- 
Toby Corkindale
Software developer
w: www.rea-group.com
REA Group refers to realestate.com.au Ltd (ASX:REA)

Warning - This e-mail transmission may contain confidential information.
If you have received this transmission in error, please notify us
immediately on (61 3) 9897 1121 or by reply email to the sender. You
must destroy the e-mail immediately and not use, copy, distribute or
disclose the contents.

```

## Johannes Sixt, 2008-04-17 10:20

Subject: Re: Maintaining commit.template config through clones
Message-ID: <48072458.70005@viscovery.net>
URL: https://gitlist.dev/e/48072458.70005%40viscovery.net
In-Reply-To: <48070EA4.2050503@rea-group.com>

```
Toby Corkindale schrieb:
> I'm attempting to implement Git at our company, and we currently use a
> commit template for CVS. I can convert this to a Git-formatted template,
> and set it for use with git-config commit.template ....
> 
> However, once the repository is cloned, this configuration option
> vanishes from .git/config
> 
> Is there a way to make configuration options sticky?

Create or edit $prefix/share/git-core/templates/config.

-- Hannes

```

## Toby Corkindale, 2008-04-22 04:45

Subject: Re: Maintaining commit.template config through clones
Message-ID: <480D6D6C.7040708@rea-group.com>
URL: https://gitlist.dev/e/480D6D6C.7040708%40rea-group.com
In-Reply-To: <48072458.70005@viscovery.net>

```
Johannes Sixt wrote:
> Toby Corkindale schrieb:
>> I'm attempting to implement Git at our company, and we currently use a
>> commit template for CVS. I can convert this to a Git-formatted template,
>> and set it for use with git-config commit.template ....
>>
>> However, once the repository is cloned, this configuration option
>> vanishes from .git/config
>>
>> Is there a way to make configuration options sticky?
> 
> Create or edit $prefix/share/git-core/templates/config.

Thanks.
Will that keep the commit-template propagated even when the repo is 
cloned from another machine? (ie. using git: or ssh: methods)

tjc.

-- 
Toby Corkindale
Software developer
w: www.rea-group.com
REA Group refers to realestate.com.au Ltd (ASX:REA)

Warning - This e-mail transmission may contain confidential information.
If you have received this transmission in error, please notify us
immediately on (61 3) 9897 1121 or by reply email to the sender. You
must destroy the e-mail immediately and not use, copy, distribute or
disclose the contents.

```

## Johannes Sixt, 2008-04-22 06:12

Subject: Re: Maintaining commit.template config through clones
Message-ID: <480D81C4.2030501@viscovery.net>
URL: https://gitlist.dev/e/480D81C4.2030501%40viscovery.net
In-Reply-To: <480D6D6C.7040708@rea-group.com>

```
Toby Corkindale schrieb:
> Johannes Sixt wrote:
>> Toby Corkindale schrieb:
>>> I'm attempting to implement Git at our company, and we currently use a
>>> commit template for CVS. I can convert this to a Git-formatted template,
>>> and set it for use with git-config commit.template ....
>>>
>>> However, once the repository is cloned, this configuration option
>>> vanishes from .git/config
>>>
>>> Is there a way to make configuration options sticky?
>>
>> Create or edit $prefix/share/git-core/templates/config.
> 
> Thanks.
> Will that keep the commit-template propagated even when the repo is
> cloned from another machine? (ie. using git: or ssh: methods)

No. You have to edit this file on each machine.

-- Hannes

```