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

[PATCH 0/2] Create a shared config file

From
Nathan W. Panike <nathan.panike@gmail.com>
Date
Nov 27, 2010, 15:00 UTC
Message-ID
<cover.1290870041.git.nathan.panike@gmail.com>

Configuration should normally be on a per-repository or per-user basis. There are cases where it would be helpful to have a project share configuration across repositories and between developers. Normally this happens only via e-mail or IRC or by word-of-mouth. The solution implemented by these patches is to have a .gitconfig file in the toplevel of the repository.

This is not a finished implementation, as I have no tests written. Instead, this is ``one way to do it.''

Nathan W. Panike (2):
  Add support for a shared config file
  Document toplevel .gitconfig file
 Documentation/config.txt |   11 ++++++++++
 builtin/config.c         |    9 +++++++-
 config.c                 |   49 +++++++++++++++++++++++++++++++++++++++++++++-
 3 files changed, 67 insertions(+), 2 deletions(-)
-- 
1.7.3.2.347.gd33a62
Next: Nathan W. Panike
Message 1 of 6 in “Create a shared config file”
  1. 0/2 Create a shared config fileNathan W. Panike, Nov 27, 2010
  2. 1/2 Add support for a shared config fileNathan W. Panike, Nov 25, 2010
  3. Thiago FarinaNov 27, 2010
  4. 2/2 Document toplevel gitconfig fileNathan W. Panike, Nov 25, 2010
  5. Jonathan NiederNov 27, 2010
  6. Nguyen Thai Ngoc DuyNov 27, 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.