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

git-config(1) should mention `git -c`

From
David Glasser <glasser@davidglasser.net>
Date
Aug 22, 2016, 18:42 UTC
Message-ID
<CAN7QDoJ-gQ9XUkCrTT6YDN+aUjNrAJWaG+WxbUvu32DJG-OZDg@mail.gmail.com>

In addition to describing the `git config` command, git-config(1) also appears to be where the algorithm for determining the active configuration values is documented, in the FILES and ENVIRONMENT sections. (There is minimal documentation of these files and environment variables in git(1).)

However, `git -c name=value` is not documented in this manpage. So to understand the full set of ways to affect the configuration of a git command, you need to know to read both git(1) and git-config(1).

I'd like to add a reference to `git -c` to git-config(1). I would happily send a patch but I'm not sure of the best place to put it — maybe in the FILES section?

--dave
-- 
glasser@davidglasser.net | langtonlabs.org | flickr.com/photos/glasser/
Next: Jeff King
Message 1 of 5 in “git-config(1) should mention `git -c`”
  1. David GlasserAug 22, 2016
  2. Jeff KingAug 22, 2016
  3. Junio C HamanoAug 23, 2016
  4. David GlasserAug 23, 2016
  5. Jeff KingAug 23, 2016

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.