June 2009
Intermediate to advanced
330 pages
9h 29m
English
Content preview from Version Control with GitBecome an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Configuration Files
Git’s configuration files are all simple text files in the
style of .ini files. They record various choices
and settings used by many Git commands. Some settings represent purely
personal preferences (should a color.pager be used?);
others are vital to a repository functioning correctly
(core.repositoryformatversion), while still others
tweak command behavior a bit (gc.auto).
Like many tools, Git supports a hierarchy of configuration files. In decreasing precedence, they are:
- .git/config
Repository-specific configuration settings manipulated with the
--fileoption or by default. These settings have the highest precedence.- ~/.gitconfig
User-specific configuration settings manipulated with the
--globaloption.- /etc/gitconfig
System-wide configuration settings manipulated with the
--systemoption if you have proper Unix file write permissions on it. These settings have the lowest precedence. Depending on your actual installation, the system settings file might be somewhere else, like /usr/local/etc/gitconfig, or it might be entirely absent.
For example, to establish an author name and email address that
will be used on all the commits that you make for all of your
repositories, configure values for user.name and
user.email in your
$HOME/.gitconfig file using git config
--global:
$git config --global user.name "Jon Loeliger"$git config --global user.email "jdl@example.com"
Or, to set a repository-specific name and email address that would
override a --global setting, simply ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.