Skip to content
This repository has been archived by the owner on May 2, 2019. It is now read-only.

Commit

Permalink
Merge commit 'adelcambre/master'
Browse files Browse the repository at this point in the history
  • Loading branch information
schacon committed Aug 3, 2009
2 parents 6f9debd + ea8db9d commit d5ef3e9
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion en/06-git-tools/01-chapter6.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -558,7 +558,7 @@ Running this command gives you a list of commits in your text editor that looks

It’s important to note that these commits are listed in the opposite order than you normally see them using the `log` command. If you run a `log`, you see something like this:

$ git log --pretty=format:"%h %s HEAD~3..HEAD"
$ git log --pretty=format:"%h %s" HEAD~3..HEAD
a5f4a0d added cat-file
310154e updated README formatting and added blame
f7f3f6d changed my name a bit
Expand Down
2 changes: 1 addition & 1 deletion en/07-customizing-git/01-chapter7.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ You saw some simple Git configuration details in the first chapter, but I’ll g

The next place Git looks is the `~/.gitconfig` file, which is specific to each user. You can make Git read and write to this file by passing the `--global` option.

Finally, Git looks for configuration values in the config file in the Git directory (`.git/config`) of whatever repository you’re currently using. These values are specific to that single repository. Each level overwrites values in the previous level, so values in `.git/config` trump those in `/etc/sysconfig`, for instance. You can also set these values by manually editing the file and inserting the correct syntax, but it’s generally easier to run the `git config` command.
Finally, Git looks for configuration values in the config file in the Git directory (`.git/config`) of whatever repository you’re currently using. These values are specific to that single repository. Each level overwrites values in the previous level, so values in `.git/config` trump those in `/etc/gitconfig`, for instance. You can also set these values by manually editing the file and inserting the correct syntax, but it’s generally easier to run the `git config` command.

### Basic Client Configuration ###

Expand Down

0 comments on commit d5ef3e9

Please sign in to comment.