{"thread":{"id":"13149","subject":"Maintaining commit.template config through clones","startedAt":"2008-04-17T08:47:32Z","lastAt":"2008-04-22T06:12:20Z","messageCount":4,"participants":["Toby Corkindale","Johannes Sixt"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"74623","messageId":"48070EA4.2050503@rea-group.com","threadId":"13149","inReplyTo":null,"subject":"Maintaining commit.template config through clones","fromName":"Toby Corkindale","fromEmail":"toby.corkindale@rea-group.com","sentAt":"2008-04-17T08:47:32Z","receivedAt":"2008-04-17T08:47:32Z","isPatch":false,"sender":{"key":"toby.corkindale@rea-group.com","avatar":null},"body":"Hi,\nI'm attempting to implement Git at our company, and we currently use a \ncommit template for CVS. I can convert this to a Git-formatted template, \nand set it for use with git-config commit.template ....\n\nHowever, once the repository is cloned, this configuration option \nvanishes from .git/config\n\nIs there a way to make configuration options sticky?\n\nthanks,\nToby\n\n-- \nToby Corkindale\nSoftware developer\nw: www.rea-group.com\nREA Group refers to realestate.com.au Ltd (ASX:REA)\n\nWarning - This e-mail transmission may contain confidential information.\nIf you have received this transmission in error, please notify us\nimmediately on (61 3) 9897 1121 or by reply email to the sender. You\nmust destroy the e-mail immediately and not use, copy, distribute or\ndisclose the contents.\n"},{"id":"74630","messageId":"48072458.70005@viscovery.net","threadId":"13149","inReplyTo":"48070EA4.2050503@rea-group.com","subject":"Re: Maintaining commit.template config through clones","fromName":"Johannes Sixt","fromEmail":"j.sixt@viscovery.net","sentAt":"2008-04-17T10:20:08Z","receivedAt":"2008-04-17T10:20:08Z","isPatch":false,"sender":{"key":"j6t@kdbg.org","avatar":"https://avatars.githubusercontent.com/u/14810926?v=4"},"body":"Toby Corkindale schrieb:\n> I'm attempting to implement Git at our company, and we currently use a\n> commit template for CVS. I can convert this to a Git-formatted template,\n> and set it for use with git-config commit.template ....\n> \n> However, once the repository is cloned, this configuration option\n> vanishes from .git/config\n> \n> Is there a way to make configuration options sticky?\n\nCreate or edit $prefix/share/git-core/templates/config.\n\n-- Hannes\n"},{"id":"74904","messageId":"480D6D6C.7040708@rea-group.com","threadId":"13149","inReplyTo":"48072458.70005@viscovery.net","subject":"Re: Maintaining commit.template config through clones","fromName":"Toby Corkindale","fromEmail":"toby.corkindale@rea-group.com","sentAt":"2008-04-22T04:45:32Z","receivedAt":"2008-04-22T04:45:32Z","isPatch":false,"sender":{"key":"toby.corkindale@rea-group.com","avatar":null},"body":"Johannes Sixt wrote:\n> Toby Corkindale schrieb:\n>> I'm attempting to implement Git at our company, and we currently use a\n>> commit template for CVS. I can convert this to a Git-formatted template,\n>> and set it for use with git-config commit.template ....\n>>\n>> However, once the repository is cloned, this configuration option\n>> vanishes from .git/config\n>>\n>> Is there a way to make configuration options sticky?\n> \n> Create or edit $prefix/share/git-core/templates/config.\n\nThanks.\nWill that keep the commit-template propagated even when the repo is \ncloned from another machine? (ie. using git: or ssh: methods)\n\ntjc.\n\n-- \nToby Corkindale\nSoftware developer\nw: www.rea-group.com\nREA Group refers to realestate.com.au Ltd (ASX:REA)\n\nWarning - This e-mail transmission may contain confidential information.\nIf you have received this transmission in error, please notify us\nimmediately on (61 3) 9897 1121 or by reply email to the sender. You\nmust destroy the e-mail immediately and not use, copy, distribute or\ndisclose the contents.\n"},{"id":"74910","messageId":"480D81C4.2030501@viscovery.net","threadId":"13149","inReplyTo":"480D6D6C.7040708@rea-group.com","subject":"Re: Maintaining commit.template config through clones","fromName":"Johannes Sixt","fromEmail":"j.sixt@viscovery.net","sentAt":"2008-04-22T06:12:20Z","receivedAt":"2008-04-22T06:12:20Z","isPatch":false,"sender":{"key":"j6t@kdbg.org","avatar":"https://avatars.githubusercontent.com/u/14810926?v=4"},"body":"Toby Corkindale schrieb:\n> Johannes Sixt wrote:\n>> Toby Corkindale schrieb:\n>>> I'm attempting to implement Git at our company, and we currently use a\n>>> commit template for CVS. I can convert this to a Git-formatted template,\n>>> and set it for use with git-config commit.template ....\n>>>\n>>> However, once the repository is cloned, this configuration option\n>>> vanishes from .git/config\n>>>\n>>> Is there a way to make configuration options sticky?\n>>\n>> Create or edit $prefix/share/git-core/templates/config.\n> \n> Thanks.\n> Will that keep the commit-template propagated even when the repo is\n> cloned from another machine? (ie. using git: or ssh: methods)\n\nNo. You have to edit this file on each machine.\n\n-- Hannes\n"}]}