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

Re: Propagating config to clones/pulls

From
NKNeal Kreitzinger <neal@rsss.com>
Date
Sep 7, 2010, 21:36 UTC
Message-ID
<i66bas$q4t$1@dough.gmane.org>
In-Reply-To
<A8F08AD5-6DB5-4A4D-9A8F-79DDBD93E666@getgosu.com>

"Douglas Tan" <douglas@getgosu.com> wrote in message news:A8F08AD5-6DB5-4A4D-9A8F-79DDBD93E666@getgosu.com...

Show 5 quoted lines
>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?--

Based on the assumption that your "child" repos are supposed to have the same .git/config files, I tried using git-init --template=x with a config file in template directory "x", but git-init only picks up the config file on an initialization of a new repo, not on a reinitialization of an existing repo.

v/r, Neal

Previous: Douglas Tan
Message 5 of 5 in “Propagating config to clones/pulls”
  1. Douglas TanSep 7, 2010
  2. Thomas RastSep 7, 2010
  3. David AguilarSep 7, 2010
  4. Douglas TanSep 8, 2010
  5. Neal KreitzingerSep 7, 2010

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.