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

Re: RFC GSoC idea: new "git config" features

From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
Mar 1, 2014, 11:01 UTC
Message-ID
<vpq38j2tc6f.fsf@anie.imag.fr>
In-Reply-To
<20140301075247.GF20397@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
> If we had the keys in-memory, we could reverse this: config code asks
> for keys it cares about, and we can do an optimized lookup (binary
> search, hash, etc).

I'm actually dreaming of a system where a configuration variable could be "declared" in Git's source code, with associated type (list/single value, boolean/string/path/...), default value and documentation (and then Documentation/config.txt could become a generated file). One could imagine a lot of possibilities like

$ git config --describe <some-variable>
Type: boolean
Default value: true
Description: ...

Somehow, do for config variables what has been done for command-line option parsing.

Migrating the whole code to such system would take time, but creating the system and applying it to a few examples might be feasible as a GSoC project.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Previous: Jeff KingNext: Jeff King
Message 5 of 8 in “RFC GSoC idea: new "git config" features”
  1. Michael HaggertyFeb 28, 2014
  2. Junio C HamanoFeb 28, 2014
  3. Michael HaggertyMar 1, 2014
  4. Jeff KingMar 1, 2014
  5. Matthieu MoyMar 1, 2014
  6. Jeff KingMar 14, 2014
  7. Junio C HamanoMar 14, 2014
  8. Junio C HamanoMar 3, 2014

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.