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

[RFC/WIP 0/3] Shared config

From
Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
Date
Dec 9, 2010, 15:09 UTC
Message-ID
<1291907388-9068-1-git-send-email-pclouds@gmail.com>

Another approach is [1]. I think this one is somewhat simpler and exposes less risk by putting the shared config under version control.

This is not complete (for example, git-prune should learn about this), but is there any serious flaw that I missed?

One thing that I haven't thought of is the shared config between subprojects. Maybe there's a better approach for subprojects.

(The resistance to nd/struct-pathspec seems great. This is the second time I come to address it and end up with something else)

[1] http://thread.gmane.org/gmane.comp.version-control.git/162309
Nguyễn Thái Ngọc Duy (3):
  config: read full file content before parsing
  config: add git_config_from_sha1() to read from a blob
  config: add core.sharedconfig
 cache.h       |    1 +
 config.c      |  110 +++++++++++++++++++++++++++++++++++++++++++--------------
 environment.c |    1 +
 3 files changed, 85 insertions(+), 27 deletions(-)
-- 
1.7.3.3.476.g893a9
Next: Nguyễn Thái Ngọc Duy
Message 1 of 11 in “[RFC/WIP 0/3] Shared config”
  1. Nguyễn Thái Ngọc DuyDec 9, 2010
  2. 1/3 config: read full file content before parsingNguyễn Thái Ngọc Duy, Dec 9, 2010
  3. 2/3 config: add git_config_from_sha1() to read from a blobNguyễn Thái Ngọc Duy, Dec 9, 2010
  4. Thiago FarinaDec 9, 2010
  5. Jonathan NiederDec 9, 2010
  6. 3/3 config: add core.sharedconfigNguyễn Thái Ngọc Duy, Dec 9, 2010
  7. Thiago FarinaDec 9, 2010
  8. Nguyen Thai Ngoc DuyDec 10, 2010
  9. Junio C HamanoDec 9, 2010
  10. Jonathan NiederDec 9, 2010
  11. Nguyen Thai Ngoc DuyDec 10, 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.