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

Re: Locally manage user/branch setting files without pushing them remotely

From
NSNicolas Sebrecht <nicolas.s.dev@gmx.fr>
Date
Nov 11, 2009, 19:24 UTC
Message-ID
<20091111192449.GH27518@vidovic>
In-Reply-To
<9accb4400911110401g5c44d011u50cafcfe736a2ec6@mail.gmail.com>
The 11/11/09, Daniele Segato wrote:
Show 5 quoted lines
> The project has a lot of setting that are really binded to the user
> and should not go pushed in a remote repository (example: database
> connections parameters / filesystem paths)
> We have a .template file for those settings but the actual settings
> are really binded to the user environment.

This looks to _not_ be a piece of the development project. Settings used for the tests suites, company where you work, etc _are_ clones (from the abstract POV, at least) of the maintainer public repository.

If you want to track changes of settings in a per-production-repo basis, you should do it _out_ of your main development repository. The latter should have a publishable template instead (eg. "user = user_login", "password = set_your_password").

-- 
Nicolas Sebrecht
Previous: Paolo CiarrocchiNext: Daniele Segato
Message 6 of 10 in “Locally manage user/branch setting files without pushing them remotely”
  1. Daniele SegatoNov 11, 2009
  2. Yann SimonNov 11, 2009
  3. Daniele SegatoNov 11, 2009
  4. Yann SimonNov 11, 2009
  5. Paolo CiarrocchiNov 11, 2009
  6. Nicolas SebrechtNov 11, 2009
  7. Daniele SegatoNov 12, 2009
  8. Nicolas SebrechtNov 12, 2009
  9. Daniele SegatoNov 12, 2009
  10. Nicolas SebrechtNov 12, 2009

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.