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

recommendations for practical git config settings for /etc/gitconfig?

From
Robert P. J. Day <rpjday@crashcourse.ca>
Date
Jun 19, 2018, 12:55 UTC
Message-ID
<alpine.LFD.2.21.1806190845170.13482@localhost.localdomain>
  updating some git course material, and i want to add to the config
section at least a small number of example config settings that make
practical sense to add to the system /etc/gitconfig file. that is,
config settings that, even if i don't explain them fully, even novice
git users will appreciate that such settings make sense to apply to
*all* users on a system.
  i imagine that would include any (corporate-mandated) settings
related to networking authentication and protocols,
filesystem-related settings and more, such as:
  * core.protect{HFS,NTFS}
  * whitespace/EOL settings
  * proxy/ssh-related commands
  * http.* settings
  * some sendemail settings

you get the idea. i don't have a ton of experience configuring git in an enterprise setting, so while there are a zillion config settings one *could* add to /etc/gitconfig, i'm interested in what experienced git admins can testify really make sense to set in a corporate environment. does that make sense?

  open to thoughts ...
rday
-- 
========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                  http://crashcourse.ca/dokuwiki

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================
Message 1 of 1 in “recommendations for practical git config settings for /etc/gitconfig?”
  1. Robert P. J. DayJun 19, 2018

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.