git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Maintaining commit.template config through clones

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Apr 22, 2008, 06:12 UTC
Message-ID
<480D81C4.2030501@viscovery.net>
In-Reply-To
<480D6D6C.7040708@rea-group.com>
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
Previous: Toby Corkindale
Message 4 of 4 in “Maintaining commit.template config through clones”
  1. Toby CorkindaleApr 17, 2008
  2. Johannes SixtApr 17, 2008
  3. Toby CorkindaleApr 22, 2008
  4. Johannes SixtApr 22, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.