git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Git Mailing list <git@vger.kernel.org>
Subject: recommendations for practical git config settings for /etc/gitconfig?
Date: Tue, 19 Jun 2018 08:55:14 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.21.1806190845170.13482@localhost.localdomain> (raw)


  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
========================================================================

                 reply	other threads:[~2018-06-19 12:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.2.21.1806190845170.13482@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).