threads / discuss / 13149

Maintaining commit.template config through clones

Subject: Maintaining commit.template config through clones

## tl;dr

4 messages between Apr 17, 2008 and Apr 22, 2008.

replies: 3people: 2as markdown or json

Toby Corkindale· Apr 17, 2008, 08:47 UTC · lore

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· Apr 17, 2008, 10:20 UTC · re: Toby Corkindale · lore

Re: Maintaining commit.template config through clones

Toby Corkindale schrieb:
Show 8 quoted lines
> 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· Apr 22, 2008, 04:45 UTC · re: Johannes Sixt · lore

Re: Maintaining commit.template config through clones

Johannes Sixt wrote:
Show 11 quoted lines
> 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· Apr 22, 2008, 06:12 UTC · re: Toby Corkindale · lore

Re: Maintaining commit.template config through clones

Toby Corkindale schrieb:
Show 16 quoted lines
> 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

← back to recent threads