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

Re: Git config multiple values

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Oct 6, 2017, 17:25 UTC
Message-ID
<20171006172530.GV19555@aiede.mtv.corp.google.com>
In-Reply-To
<20171006143219.4bn63aoenluc77fd@sigill.intra.peff.net>
Hi,
Jeff King wrote:
> On Fri, Oct 06, 2017 at 01:10:17PM +0200, aleksander.baranowski wrote:
Show 6 quoted lines
>> It's just an opinion, but this behaviour is no consistent for me.
>>
>> If it's not the bug it's a feature just let me know.
>
> It's a feature, though I agree that git-config is rather baroque. We're
> mostly stuck with it for reasons of backwards compatibility, though.

This feels like a dodge. Can we make a list of what is baroque here, with an eye to fixing it? E.g. if we introduce a new --set option, then what should its semantics be, to be more intuitive?

Thanks, Jonathan

Previous: aleksander.baranowskiNext: Jeff King
Message 4 of 6 in “Git config multiple values”
  1. aleksander.baranowskiOct 6, 2017
  2. Jeff KingOct 6, 2017
  3. aleksander.baranowskiOct 6, 2017
  4. Jonathan NiederOct 6, 2017
  5. Jeff KingOct 6, 2017
  6. Andreas HeidukOct 6, 2017

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.