提交: 9f55b90e9831821d572fd927a3bd008aa3ba3c14 - mytools (git)

Commit MetaInfo

• 修訂: 9f55b90e9831821d572fd927a3bd008aa3ba3c14 (tree)
• 時間: 2020-10-25 09:39:14
• 作者: matsuand <30614168+matsuand@user...>
• Commiter: matsuand

Log Message

修正。20201025結果追加。

Change Summary

• add: progit2ja_diff/20201025.result.txt
• modified: progit2ja_diff/progit2ja_diff.perl

差異

--- /dev/null
+++ b/progit2ja_diff/20201025.result.txt
@@ -0,0 +1,20598 @@
+diff -au ../../git/progit2/progit2/A-git-in-other-environments.asc /tmp/A-git-in-other-environments.asc.tmp
+--- ../../git/progit2/progit2/A-git-in-other-environments.asc	2020-08-29 09:58:24.046195489 +0900
++++ /tmp/A-git-in-other-environments.asc.tmp	2020-10-25 09:24:25.507959693 +0900
+@@ -1,4 +1,4 @@
+-[[A-git-in-other-environments]]
++[#A-git-in-other-environments]
+ [appendix]
+ == Git in Other Environments
+ 
+@@ -7,22 +7,6 @@
+ But the story doesn't end there; Git is usually used as part of a larger ecosystem, and the terminal isn't always the best way to work with it.
+ Now we'll take a look at some of the other kinds of environments where Git can be useful, and how other applications (including yours) work alongside Git.
+ 
+-include::book/A-git-in-other-environments/sections/guis.asc[]
+-
+-include::book/A-git-in-other-environments/sections/visualstudio.asc[]
+-
+-include::book/A-git-in-other-environments/sections/visualstudiocode.asc[]
+-
+-include::book/A-git-in-other-environments/sections/jetbrainsides.asc[]
+-
+-include::book/A-git-in-other-environments/sections/sublimetext.asc[]
+-
+-include::book/A-git-in-other-environments/sections/bash.asc[]
+-
+-include::book/A-git-in-other-environments/sections/zsh.asc[]
+-
+-include::book/A-git-in-other-environments/sections/powershell.asc[]
+-
+ === Summary
+ 
+ You've learned how to harness Git's power from inside the tools that you use during your everyday work, and also how to access Git repositories from your own programs.
+Warning: file not found: ../../git/progit2/progit2-ja/B-embedding-git-in-your-applications.asc
+diff -au ../../git/progit2/progit2/C-git-commands.asc /tmp/C-git-commands.asc.tmp
+--- ../../git/progit2/progit2/C-git-commands.asc	2020-08-17 16:38:51.074694961 +0900
++++ /tmp/C-git-commands.asc.tmp	2020-10-25 09:24:25.545961483 +0900
+@@ -1,4 +1,4 @@
+-[[C-git-commands]]
++[#C-git-commands]
+ [appendix]
+ == Git Commands
+ 
+@@ -8,20 +8,10 @@
+ In this appendix, we'll go through all the Git commands we addressed throughout the book, grouped roughly by what they're used for.
+ We'll talk about what each command very generally does and then point out where in the book you can find us having used it.
+ 
+-[TIP]
+-====
+-You can abbreviate long options.
+-For example, you can type in `git commit --a`, which acts as if you typed `git commit --amend`.
+-This only works when the letters after `--` are unique for one option.
+-Do use the full option when writing scripts.
+-====
+-
+ === Setup and Config
+ 
+ There are two commands that are used quite a lot, from the first invocations of Git to common every day tweaking and referencing, the `config` and `help` commands.
+ 
+-==== git config
+-
+ Git has a default way of doing hundreds of things.
+ For a lot of these things, you can tell Git to default to doing them a different way, or set your preferences.
+ This involves everything from telling Git what your name is to specific terminal color preferences or what editor you use.
+@@ -29,251 +19,178 @@
+ 
+ The `git config` command has been used in nearly every chapter of the book.
+ 
+-In <<ch01-getting-started#_first_time>> we used it to specify our name, email address and editor preference before we even got started using Git.
++In <<ch01-introduction#r_first_time>> we used it to specify our name, email address and editor preference before we even got started using Git.
+ 
+-In <<ch02-git-basics-chapter#_git_aliases>> we showed how you could use it to create shorthand commands that expand to long option sequences so you don't have to type them every time.
++In <<ch02-git-basics#r_git_aliases>> we showed how you could use it to create shorthand commands that expand to long option sequences so you don't have to type them every time.
+ 
+-In <<ch03-git-branching#_rebasing>> we used it to make `--rebase` the default when you run `git pull`.
++In <<ch03-git-branching#r_rebasing>> we used it to make `--rebase` the default when you run `git pull`.
+ 
+-In <<ch07-git-tools#_credential_caching>> we used it to set up a default store for your HTTP passwords.
++In <<ch07-git-tools#r_credential_caching>> we used it to set up a default store for your HTTP passwords.
+ 
+-In <<ch08-customizing-git#_keyword_expansion>> we showed how to set up smudge and clean filters on content coming in and out of Git.
+-
+-Finally, basically the entirety of <<ch08-customizing-git#_git_config>> is dedicated to the command.
+-
+-[[_core_editor]]
+-==== git config core.editor commands
+-
+-Accompanying the configuration instructions in <<ch01-getting-started#_editor>>, many editors can be set as follows:
+-
+-.Exhaustive list of `core.editor` configuration commands
+-[cols="1,2",options="header"]
+-|==============================
+-|Editor | Configuration command
+-|Atom |`git config --global core.editor "atom --wait"`
+-|BBEdit (Mac, with command line tools) |`git config --global core.editor "bbedit -w"`
+-|Emacs |`git config --global core.editor emacs`
+-|Gedit (Linux) |`git config --global core.editor "gedit --wait --new-window"`
+-|Gvim (Windows 64-bit) |`git config --global core.editor "'C:\Program Files\Vim\vim72\gvim.exe' --nofork '%*'"` (Also see note below)
+-|Kate (Linux) |`git config --global core.editor "kate"`
+-|nano |`git config --global core.editor "nano -w"`
+-|Notepad (Windows 64-bit) |`git config core.editor notepad`
+-|Notepad++ (Windows 64-bit) |`git config --global core.editor "'C:\Program Files\Notepad++\notepad++.exe' -multiInst -notabbar -nosession -noPlugin"` (Also see note below)
+-|Scratch (Linux)|`git config --global core.editor "scratch-text-editor"`
+-|Sublime Text (macOS) |`git config --global core.editor "/Applications/Sublime\ Text.app/Contents/SharedSupport/bin/subl --new-window --wait"`
+-|Sublime Text (Windows 64-bit) |`git config --global core.editor "'C:\Program Files\Sublime Text 3\sublime_text.exe' -w"` (Also see note below)
+-|TextEdit (macOS)|`git config --global --add core.editor "open -W -n"`
+-|Textmate |`git config --global core.editor "mate -w"`
+-|Textpad (Windows 64-bit) |`git config --global core.editor "'C:\Program Files\TextPad 5\TextPad.exe' -m` (Also see note below)
+-|UltraEdit (Windows 64-bit) | `git config --global core.editor Uedit32`
+-|Vim |`git config --global core.editor "vim"`
+-|Visual Studio Code |`git config --global core.editor "code --wait"`
+-|VSCodium (Free/Libre Open Source Software Binaries of VSCode) | `git config --global core.editor "codium --wait"`
+-|WordPad |`git config --global core.editor '"C:\Program Files\Windows NT\Accessories\wordpad.exe"'"`
+-|Xi | `git config --global core.editor "xi --wait"`
+-|==============================
+-
+-[NOTE]
+-====
+-If you have a 32-bit editor on a Windows 64-bit system, the program will be installed in `C:\Program Files (x86)\` rather than `C:\Program Files\` as in the table above.
+-====
++In <<ch08-customizing-git#r_keyword_expansion>> we showed how to set up smudge and clean filters on content coming in and out of Git.
+ 
+-==== git help
++Finally, basically the entirety of <<ch08-customizing-git#r_git_config>> is dedicated to the command.
+ 
+ The `git help` command is used to show you all the documentation shipped with Git about any command.
+ While we're giving a rough overview of most of the more popular ones in this appendix, for a full listing of all of the possible options and flags for every command, you can always run `git help <command>`.
+ 
+-We introduced the `git help` command in <<ch01-getting-started#_git_help>> and showed you how to use it to find more information about the `git shell` in <<ch04-git-on-the-server#_setting_up_server>>.
+-
++We introduced the `git help` command in <<ch01-introduction#r_git_help>> and showed you how to use it to find more information about the `git shell` in <<ch04-git-server#r_setting_up_server>>.
+ 
+ === Getting and Creating Projects
+ 
+ There are two ways to get a Git repository.
+ One is to copy it from an existing repository on the network or elsewhere and the other is to create a new one in an existing directory.
+ 
+-==== git init
+-
+ To take a directory and turn it into a new Git repository so you can start version controlling it, you can simply run `git init`.
+ 
+-We first introduce this in <<ch02-git-basics-chapter#_getting_a_repo>>, where we show creating a brand new repository to start working with.
++We first introduce this in <<ch02-git-basics#r_getting_a_repo>>, where we show creating a brand new repository to start working with.
+ 
+-We talk briefly about how you can change the default branch name from ``master'' in <<ch03-git-branching#_remote_branches>>.
++We talk briefly about how you can change the default branch from ``master'' in <<ch03-git-branching#r_remote_branches>>.
+ 
+-We use this command to create an empty bare repository for a server in <<ch04-git-on-the-server#_bare_repo>>.
++We use this command to create an empty bare repository for a server in <<ch04-git-server#r_bare_repo>>.
+ 
+-Finally, we go through some of the details of what it actually does behind the scenes in <<ch10-git-internals#_plumbing_porcelain>>.
+-
+-==== git clone
++Finally, we go through some of the details of what it actually does behind the scenes in <<ch10-git-internals#r_plumbing_porcelain>>.
+ 
+ The `git clone` command is actually something of a wrapper around several other commands.
+ It creates a new directory, goes into it and runs `git init` to make it an empty Git repository, adds a remote (`git remote add`) to the URL that you pass it (by default named `origin`), runs a `git fetch` from that remote repository and then checks out the latest commit into your working directory with `git checkout`.
+ 
+ The `git clone` command is used in dozens of places throughout the book, but we'll just list a few interesting places.
+ 
+-It's basically introduced and explained in <<ch02-git-basics-chapter#_git_cloning>>, where we go through a few examples.
++It's basically introduced and explained in <<ch02-git-basics#r_git_cloning>>, where we go through a few examples.
+ 
+-In <<ch04-git-on-the-server#_getting_git_on_a_server>> we look at using the `--bare` option to create a copy of a Git repository with no working directory.
++In <<ch04-git-server#r_git_on_the_server>> we look at using the `--bare` option to create a copy of a Git repository with no working directory.
+ 
+-In <<ch07-git-tools#_bundling>> we use it to unbundle a bundled Git repository.
++In <<ch07-git-tools#r_bundling>> we use it to unbundle a bundled Git repository.
+ 
+-Finally, in <<ch07-git-tools#_cloning_submodules>> we learn the `--recurse-submodules` option to make cloning a repository with submodules a little simpler.
++Finally, in <<ch07-git-tools#r_cloning_submodules>> we learn the `--recursive` option to make cloning a repository with submodules a little simpler.
+ 
+ Though it's used in many other places through the book, these are the ones that are somewhat unique or where it is used in ways that are a little different.
+ 
+-
+ === Basic Snapshotting
+ 
+ For the basic workflow of staging content and committing it to your history, there are only a few basic commands.
+ 
+-==== git add
+-
+ The `git add` command adds content from the working directory into the staging area (or ``index'') for the next commit.
+ When the `git commit` command is run, by default it only looks at this staging area, so `git add` is used to craft what exactly you would like your next commit snapshot to look like.
+ 
+ This command is an incredibly important command in Git and is mentioned or used dozens of times in this book.
+ We'll quickly cover some of the unique uses that can be found.
+ 
+-We first introduce and explain `git add` in detail in <<ch02-git-basics-chapter#_tracking_files>>.
++We first introduce and explain `git add` in detail in <<ch02-git-basics#r_tracking_files>>.
+ 
+-We mention how to use it to resolve merge conflicts in <<ch03-git-branching#_basic_merge_conflicts>>.
++We mention how to use it to resolve merge conflicts in <<ch03-git-branching#r_basic_merge_conflicts>>.
+ 
+-We go over using it to interactively stage only specific parts of a modified file in <<ch07-git-tools#_interactive_staging>>.
++We go over using it to interactively stage only specific parts of a modified file in <<ch07-git-tools#r_interactive_staging>>.
+ 
+-Finally, we emulate it at a low level in <<ch10-git-internals#_tree_objects>>, so you can get an idea of what it's doing behind the scenes.
+-
+-==== git status
++Finally, we emulate it at a low level in <<ch10-git-internals#r_tree_objects>>, so you can get an idea of what it's doing behind the scenes.
+ 
+ The `git status` command will show you the different states of files in your working directory and staging area.
+ Which files are modified and unstaged and which are staged but not yet committed.
+ In its normal form, it also will show you some basic hints on how to move files between these stages.
+ 
+-We first cover `status` in <<ch02-git-basics-chapter#_checking_status>>, both in its basic and simplified forms.
++We first cover `status` in <<ch02-git-basics#r_checking_status>>, both in its basic and simplified forms.
+ While we use it throughout the book, pretty much everything you can do with the `git status` command is covered there.
+ 
+-==== git diff
+-
+ The `git diff` command is used when you want to see differences between any two trees.
+ This could be the difference between your working environment and your staging area (`git diff` by itself), between your staging area and your last commit (`git diff --staged`), or between two commits (`git diff master branchB`).
+ 
+-We first look at the basic uses of `git diff` in <<ch02-git-basics-chapter#_git_diff_staged>>, where we show how to see what changes are staged and which are not yet staged.
+-
+-We use it to look for possible whitespace issues before committing with the `--check` option in <<ch05-distributed-git#_commit_guidelines>>.
++We first look at the basic uses of `git diff` in <<ch02-git-basics#r_git_diff_staged>>, where we show how to see what changes are staged and which are not yet staged.
+ 
+-We see how to check the differences between branches more effectively with the `git diff A...B` syntax in <<ch05-distributed-git#_what_is_introduced>>.
++We use it to look for possible whitespace issues before committing with the `--check` option in <<ch05-distributed-git#r_commit_guidelines>>.
+ 
+-We use it to filter out whitespace differences with `-b` and how to compare different stages of conflicted files with `--theirs`, `--ours` and `--base` in <<ch07-git-tools#_advanced_merging>>.
++We see how to check the differences between branches more effectively with the `git diff A...B` syntax in <<ch05-distributed-git#r_what_is_introduced>>.
+ 
+-Finally, we use it to effectively compare submodule changes with `--submodule` in <<ch07-git-tools#_starting_submodules>>.
++We use it to filter out whitespace differences with `-b` and how to compare different stages of conflicted files with `--theirs`, `--ours` and `--base` in <<ch07-git-tools#r_advanced_merging>>.
+ 
+-==== git difftool
++Finally, we use it to effectively compare submodule changes with `--submodule` in <<ch07-git-tools#r_starting_submodules>>.
+ 
+ The `git difftool` command simply launches an external tool to show you the difference between two trees in case you want to use something other than the built in `git diff` command.
+ 
+-We only briefly mention this in <<ch02-git-basics-chapter#_git_diff_staged>>.
+-
+-==== git commit
++We only briefly mention this in <<ch02-git-basics#r_git_diff_staged>>.
+ 
+ The `git commit` command takes all the file contents that have been staged with `git add` and records a new permanent snapshot in the database and then moves the branch pointer on the current branch up to it.
+ 
+-We first cover the basics of committing in <<ch02-git-basics-chapter#_committing_changes>>.
++We first cover the basics of committing in <<ch02-git-basics#r_committing_changes>>.
+ There we also demonstrate how to use the `-a` flag to skip the `git add` step in daily workflows and how to use the `-m` flag to pass a commit message in on the command line instead of firing up an editor.
+ 
+-In <<ch02-git-basics-chapter#_undoing>> we cover using the `--amend` option to redo the most recent commit.
+-
+-In <<ch03-git-branching#_git_branches_overview>>, we go into much more detail about what `git commit` does and why it does it like that.
++In <<ch02-git-basics#r_undoing>> we cover using the `--amend` option to redo the most recent commit.
+ 
+-We looked at how to sign commits cryptographically with the `-S` flag in <<ch07-git-tools#_signing_commits>>.
++In <<ch03-git-branching#r_git_branches_overview>>, we go into much more detail about what `git commit` does and why it does it like that.
+ 
+-Finally, we take a look at what the `git commit` command does in the background and how it's actually implemented in <<ch10-git-internals#_git_commit_objects>>.
++We looked at how to sign commits cryptographically with the `-S` flag in <<ch07-git-tools#r_signing_commits>>.
+ 
+-==== git reset
++Finally, we take a look at what the `git commit` command does in the background and how it's actually implemented in <<ch10-git-internals#r_git_commit_objects>>.
+ 
+ The `git reset` command is primarily used to undo things, as you can possibly tell by the verb.
+ It moves around the `HEAD` pointer and optionally changes the `index` or staging area and can also optionally change the working directory if you use `--hard`.
+ This final option makes it possible for this command to lose your work if used incorrectly, so make sure you understand it before using it.
+ 
+-We first effectively cover the simplest use of `git reset` in <<ch02-git-basics-chapter#_unstaging>>, where we use it to unstage a file we had run `git add` on.
+-
+-We then cover it in quite some detail in <<ch07-git-tools#_git_reset>>, which is entirely devoted to explaining this command.
++We first effectively cover the simplest use of `git reset` in <<ch02-git-basics#r_unstaging>>, where we use it to unstage a file we had run `git add` on.
+ 
+-We use `git reset --hard` to abort a merge in <<ch07-git-tools#_abort_merge>>, where we also use `git merge --abort`, which is a bit of a wrapper for the `git reset` command.
++We then cover it in quite some detail in <<ch07-git-tools#r_git_reset>>, which is entirely devoted to explaining this command.
+ 
+-==== git rm
++We use `git reset --hard` to abort a merge in <<ch07-git-tools#r_abort_merge>>, where we also use `git merge --abort`, which is a bit of a wrapper for the `git reset` command.
+ 
+ The `git rm` command is used to remove files from the staging area and working directory for Git.
+ It is similar to `git add` in that it stages a removal of a file for the next commit.
+ 
+-We cover the `git rm` command in some detail in <<ch02-git-basics-chapter#_removing_files>>, including recursively removing files and only removing files from the staging area but leaving them in the working directory with `--cached`.
++We cover the `git rm` command in some detail in <<ch02-git-basics#r_removing_files>>, including recursively removing files and only removing files from the staging area but leaving them in the working directory with `--cached`.
+ 
+-The only other differing use of `git rm` in the book is in <<ch10-git-internals#_removing_objects>> where we briefly use and explain the `--ignore-unmatch` when running `git filter-branch`, which simply makes it not error out when the file we are trying to remove doesn't exist.
++The only other differing use of `git rm` in the book is in <<ch10-git-internals#r_removing_objects>> where we briefly use and explain the `--ignore-unmatch` when running `git filter-branch`, which simply makes it not error out when the file we are trying to remove doesn't exist.
+ This can be useful for scripting purposes.
+ 
+-==== git mv
+-
+ The `git mv` command is a thin convenience command to move a file and then run `git add` on the new file and `git rm` on the old file.
+ 
+-We only briefly mention this command in <<ch02-git-basics-chapter#_git_mv>>.
+-
+-==== git clean
++We only briefly mention this command in <<ch02-git-basics#r_git_mv>>.
+ 
+ The `git clean` command is used to remove unwanted files from your working directory.
+ This could include removing temporary build artifacts or merge conflict files.
+ 
+-We cover many of the options and scenarios in which you might used the clean command in <<ch07-git-tools#_git_clean>>.
++We cover many of the options and scenarios in which you might used the clean command in <<ch07-git-tools#r_git_clean>>.
+ 
+ === Branching and Merging
+ 
+ There are just a handful of commands that implement most of the branching and merging functionality in Git.
+ 
+-==== git branch
+-
+ The `git branch` command is actually something of a branch management tool.
+ It can list the branches you have, create a new branch, delete branches and rename branches.
+ 
+ Most of <<ch03-git-branching#ch03-git-branching>> is dedicated to the `branch` command and it's used throughout the entire chapter.
+-We first introduce it in <<ch03-git-branching#_create_new_branch>> and we go through most of its other features (listing and deleting) in <<ch03-git-branching#_branch_management>>.
+-
+-In <<ch03-git-branching#_tracking_branches>> we use the `git branch -u` option to set up a tracking branch.
++We first introduce it in <<ch03-git-branching#r_create_new_branch>> and we go through most of its other features (listing and deleting) in <<ch03-git-branching#r_branch_management>>.
+ 
+-Finally, we go through some of what it does in the background in <<ch10-git-internals#_git_refs>>.
++In <<ch03-git-branching#r_tracking_branches>> we use the `git branch -u` option to set up a tracking branch.
+ 
+-==== git checkout
++Finally, we go through some of what it does in the background in <<ch10-git-internals#r_git_refs>>.
+ 
+ The `git checkout` command is used to switch branches and check content out into your working directory.
+ 
+-We first encounter the command in <<ch03-git-branching#_switching_branches>> along with the `git branch` command.
++We first encounter the command in <<ch03-git-branching#r_switching_branches>> along with the `git branch` command.
+ 
+-We see how to use it to start tracking branches with the `--track` flag in <<ch03-git-branching#_tracking_branches>>.
++We see how to use it to start tracking branches with the `--track` flag in <<ch03-git-branching#r_tracking_branches>>.
+ 
+-We use it to reintroduce file conflicts with `--conflict=diff3` in <<ch07-git-tools#_checking_out_conflicts>>.
++We use it to reintroduce file conflicts with `--conflict=diff3` in <<ch07-git-tools#r_checking_out_conflicts>>.
+ 
+-We go into closer detail on its relationship with `git reset` in <<ch07-git-tools#_git_reset>>.
++We go into closer detail on its relationship with `git reset` in <<ch07-git-tools#r_git_reset>>.
+ 
+-Finally, we go into some implementation detail in <<ch10-git-internals#ref_the_ref>>.
+-
+-==== git merge
++Finally, we go into some implementation detail in <<ch10-git-internals#r_the_head>>.
+ 
+ The `git merge` tool is used to merge one or more branches into the branch you have checked out.
+ It will then advance the current branch to the result of the merge.
+ 
+-The `git merge` command was first introduced in <<ch03-git-branching#_basic_branching>>.
++The `git merge` command was first introduced in <<ch03-git-branching#r_basic_branching>>.
+ Though it is used in various places in the book, there are very few variations of the `merge` command -- generally just `git merge <branch>` with the name of the single branch you want to merge in.
+ 
+-We covered how to do a squashed merge (where Git merges the work but pretends like it's just a new commit without recording the history of the branch you're merging in) at the very end of <<ch05-distributed-git#_public_project>>.
+-
+-We went over a lot about the merge process and command, including the `-Xignore-space-change` command and the `--abort` flag to abort a problem merge in <<ch07-git-tools#_advanced_merging>>.
++We covered how to do a squashed merge (where Git merges the work but pretends like it's just a new commit without recording the history of the branch you're merging in) at the very end of <<ch05-distributed-git#r_public_project>>.
+ 
+-We learned how to verify signatures before merging if your project is using GPG signing in <<ch07-git-tools#_signing_commits>>.
++We went over a lot about the merge process and command, including the `-Xignore-space-change` command and the `--abort` flag to abort a problem merge in <<ch07-git-tools#r_advanced_merging>>.
+ 
+-Finally, we learned about Subtree merging in <<ch07-git-tools#_subtree_merge>>.
++We learned how to verify signatures before merging if your project is using GPG signing in <<ch07-git-tools#r_signing_commits>>.
+ 
+-==== git mergetool
++Finally, we learned about Subtree merging in <<ch07-git-tools#r_subtree_merge>>.
+ 
+ The `git mergetool` command simply launches an external merge helper in case you have issues with a merge in Git.
+ 
+-We mention it quickly in <<ch03-git-branching#_basic_merge_conflicts>> and go into detail on how to implement your own external merge tool in <<ch08-customizing-git#_external_merge_tools>>.
+-
+-==== git log
++We mention it quickly in <<ch03-git-branching#r_basic_merge_conflicts>> and go into detail on how to implement your own external merge tool in <<ch08-customizing-git#r_external_merge_tools>>.
+ 
+ The `git log` command is used to show the reachable recorded history of a project from the most recent commit snapshot backwards.
+ By default it will only show the history of the branch you're currently on, but can be given different or even multiple heads or branches from which to traverse.
+@@ -281,305 +198,244 @@
+ 
+ This command is used in nearly every chapter of the book to demonstrate the history of a project.
+ 
+-We introduce the command and cover it in some depth in <<ch02-git-basics-chapter#_viewing_history>>.
++We introduce the command and cover it in some depth in <<ch02-git-basics#r_viewing_history>>.
+ There we look at the `-p` and `--stat` option to get an idea of what was introduced in each commit and the `--pretty` and `--oneline` options to view the history more concisely, along with some simple date and author filtering options.
+ 
+-In <<ch03-git-branching#_create_new_branch>> we use it with the `--decorate` option to easily visualize where our branch pointers are located and we also use the `--graph` option to see what divergent histories look like.
++In <<ch03-git-branching#r_create_new_branch>> we use it with the `--decorate` option to easily visualize where our branch pointers are located and we also use the `--graph` option to see what divergent histories look like.
+ 
+-In <<ch05-distributed-git#_private_team>> and <<ch07-git-tools#_commit_ranges>> we cover the `branchA..branchB` syntax to use the `git log` command to see what commits are unique to a branch relative to another branch.
+-In <<ch07-git-tools#_commit_ranges>> we go through this fairly extensively.
++In <<ch05-distributed-git#r_private_team>> and <<ch07-git-tools#r_commit_ranges>> we cover the `branchA..branchB` syntax to use the `git log` command to see what commits are unique to a branch relative to another branch.
++In <<ch07-git-tools#r_commit_ranges>> we go through this fairly extensively.
+ 
+-In <<ch07-git-tools#_merge_log>> and <<ch07-git-tools#_triple_dot>> we cover using the `branchA...branchB` format and the `--left-right` syntax to see what is in one branch or the other but not in both.
+-In <<ch07-git-tools#_merge_log>> we also look at how to use the `--merge` option to help with merge conflict debugging as well as using the `--cc` option to look at merge commit conflicts in your history.
++In <<ch07-git-tools#r_merge_log>> and <<ch07-git-tools#r_triple_dot>> we cover using the `branchA...branchB` format and the `--left-right` syntax to see what is in one branch or the other but not in both.
++In <<ch07-git-tools#r_merge_log>> we also look at how to use the `--merge` option to help with merge conflict debugging as well as using the `--cc` option to look at merge commit conflicts in your history.
+ 
+-In <<ch07-git-tools#_git_reflog>> we use the `-g` option to view the Git reflog through this tool instead of doing branch traversal.
++In <<ch07-git-tools#r_git_reflog>> we use the `-g` option to view the Git reflog through this tool instead of doing branch traversal.
+ 
+-In <<ch07-git-tools#_searching>> we look at using the `-S` and `-L` options to do fairly sophisticated searches for something that happened historically in the code such as seeing the history of a function.
++In <<ch07-git-tools#r_searching>> we look at using the `-S` and `-L` options to do fairly sophisticated searches for something that happened historically in the code such as seeing the history of a function.
+ 
+-In <<ch07-git-tools#_signing_commits>> we see how to use `--show-signature` to add a validation string to each commit in the `git log` output based on if it was validly signed or not.
+-
+-==== git stash
++In <<ch07-git-tools#r_signing_commits>> we see how to use `--show-signature` to add a validation string to each commit in the `git log` output based on if it was validly signed or not.
+ 
+ The `git stash` command is used to temporarily store uncommitted work in order to clean out your working directory without having to commit unfinished work on a branch.
+ 
+-This is basically entirely covered in <<ch07-git-tools#_git_stashing>>.
+-
+-==== git tag
++This is basically entirely covered in <<ch07-git-tools#r_git_stashing>>.
+ 
+ The `git tag` command is used to give a permanent bookmark to a specific point in the code history.
+ Generally this is used for things like releases.
+ 
+-This command is introduced and covered in detail in <<ch02-git-basics-chapter#_git_tagging>> and we use it in practice in <<ch05-distributed-git#_tagging_releases>>.
+-
+-We also cover how to create a GPG signed tag with the `-s` flag and verify one with the `-v` flag in <<ch07-git-tools#_signing>>.
++This command is introduced and covered in detail in <<ch02-git-basics#r_git_tagging>> and we use it in practice in <<ch05-distributed-git#r_tagging_releases>>.
+ 
++We also cover how to create a GPG signed tag with the `-s` flag and verify one with the `-v` flag in <<ch07-git-tools#r_signing>>.
+ 
+ === Sharing and Updating Projects
+ 
+ There are not very many commands in Git that access the network, nearly all of the commands operate on the local database.
+ When you are ready to share your work or pull changes from elsewhere, there are a handful of commands that deal with remote repositories.
+ 
+-==== git fetch
+-
+ The `git fetch` command communicates with a remote repository and fetches down all the information that is in that repository that is not in your current one and stores it in your local database.
+ 
+-We first look at this command in <<ch02-git-basics-chapter#_fetching_and_pulling>> and we continue to see examples of its use in <<ch03-git-branching#_remote_branches>>.
+-
+-We also use it in several of the examples in <<ch05-distributed-git#_contributing_project>>.
++We first look at this command in <<ch02-git-basics#r_fetching_and_pulling>> and we continue to see examples of it use in <<ch03-git-branching#r_remote_branches>>.
+ 
+-We use it to fetch a single specific reference that is outside of the default space in <<ch06-github#_pr_refs>> and we see how to fetch from a bundle in <<ch07-git-tools#_bundling>>.
++We also use it in several of the examples in <<ch05-distributed-git#r_contributing_project>>.
+ 
+-We set up highly custom refspecs in order to make `git fetch` do something a little different than the default in <<ch10-git-internals#_refspec>>.
++We use it to fetch a single specific reference that is outside of the default space in <<ch06-github#r_pr_refs>> and we see how to fetch from a bundle in <<ch07-git-tools#r_bundling>>.
+ 
+-==== git pull
++We set up highly custom refspecs in order to make `git fetch` do something a little different than the default in <<ch10-git-internals#r_refspec>>.
+ 
+ The `git pull` command is basically a combination of the `git fetch` and `git merge` commands, where Git will fetch from the remote you specify and then immediately try to merge it into the branch you're on.
+ 
+-We introduce it quickly in <<ch02-git-basics-chapter#_fetching_and_pulling>> and show how to see what it will merge if you run it in <<ch02-git-basics-chapter#_inspecting_remote>>.
+-
+-We also see how to use it to help with rebasing difficulties in <<ch03-git-branching#_rebase_rebase>>.
++We introduce it quickly in <<ch02-git-basics#r_fetching_and_pulling>> and show how to see what it will merge if you run it in <<ch02-git-basics#r_inspecting_remote>>.
+ 
+-We show how to use it with a URL to pull in changes in a one-off fashion in <<ch05-distributed-git#_checking_out_remotes>>.
++We also see how to use it to help with rebasing difficulties in <<ch03-git-branching#r_rebase_rebase>>.
+ 
+-Finally, we very quickly mention that you can use the `--verify-signatures` option to it in order to verify that commits you are pulling have been GPG signed in <<ch07-git-tools#_signing_commits>>.
++We show how to use it with a URL to pull in changes in a one-off fashion in <<ch05-distributed-git#r_checking_out_remotes>>.
+ 
+-==== git push
++Finally, we very quickly mention that you can use the `--verify-signatures` option to it in order to verify that commits you are pulling have been GPG signed in <<ch07-git-tools#r_signing_commits>>.
+ 
+ The `git push` command is used to communicate with another repository, calculate what your local database has that the remote one does not, and then pushes the difference into the other repository.
+ It requires write access to the other repository and so normally is authenticated somehow.
+ 
+-We first look at the `git push` command in <<ch02-git-basics-chapter#_pushing_remotes>>.
++We first look at the `git push` command in <<ch02-git-basics#r_pushing_remotes>>.
+ Here we cover the basics of pushing a branch to a remote repository.
+-In <<ch03-git-branching#_pushing_branches>> we go a little deeper into pushing specific branches and in <<ch03-git-branching#_tracking_branches>> we see how to set up tracking branches to automatically push to.
+-In <<ch03-git-branching#_delete_branches>> we use the `--delete` flag to delete a branch on the server with `git push`.
++In <<ch03-git-branching#r_pushing_branches>> we go a little deeper into pushing specific branches and in <<ch03-git-branching#r_tracking_branches>> we see how to set up tracking branches to automatically push to.
++In <<ch03-git-branching#r_delete_branches>> we use the `--delete` flag to delete a branch on the server with `git push`.
+ 
+-Throughout <<ch05-distributed-git#_contributing_project>> we see several examples of using `git push` to share work on branches through multiple remotes.
++Throughout <<ch05-distributed-git#r_contributing_project>> we see several examples of using `git push` to share work on branches through multiple remotes.
+ 
+-We see how to use it to share tags that you have made with the `--tags` option in <<ch02-git-basics-chapter#_sharing_tags>>.
++We see how to use it to share tags that you have made with the `--tags` option in <<ch02-git-basics#r_sharing_tags>>.
+ 
+-In <<ch07-git-tools#_publishing_submodules>> we use the `--recurse-submodules` option to check that all of our submodules work has been published before pushing the superproject, which can be really helpful when using submodules.
++In <<ch07-git-tools#r_publishing_submodules>> we use the `--recurse-submodules` option to check that all of our submodules work has been published before pushing the superproject, which can be really helpful when using submodules.
+ 
+-In <<ch08-customizing-git#_other_client_hooks>> we talk briefly about the `pre-push` hook, which is a script we can setup to run before a push completes to verify that it should be allowed to push.
++In <<ch08-customizing-git#r_other_client_hooks>> we talk briefly about the `pre-push` hook, which is a script we can setup to run before a push completes to verify that it should be allowed to push.
+ 
+-Finally, in <<ch10-git-internals#_pushing_refspecs>> we look at pushing with a full refspec instead of the general shortcuts that are normally used.
++Finally, in <<ch10-git-internals#r_pushing_refspecs>> we look at pushing with a full refspec instead of the general shortcuts that are normally used.
+ This can help you be very specific about what work you wish to share.
+ 
+-==== git remote
+-
+ The `git remote` command is a management tool for your record of remote repositories.
+ It allows you to save long URLs as short handles, such as ``origin'' so you don't have to type them out all the time.
+ You can have several of these and the `git remote` command is used to add, change and delete them.
+ 
+-This command is covered in detail in <<ch02-git-basics-chapter#_remote_repos>>, including listing, adding, removing and renaming them.
++This command is covered in detail in <<ch02-git-basics#r_remote_repos>>, including listing, adding, removing and renaming them.
+ 
+ It is used in nearly every subsequent chapter in the book too, but always in the standard `git remote add <name> <url>` format.
+ 
+-==== git archive
+-
+ The `git archive` command is used to create an archive file of a specific snapshot of the project.
+ 
+-We use `git archive` to create a tarball of a project for sharing in <<ch05-distributed-git#_preparing_release>>.
+-
+-==== git submodule
++We use `git archive` to create a tarball of a project for sharing in <<ch05-distributed-git#r_preparing_release>>.
+ 
+ The `git submodule` command is used to manage external repositories within a normal repositories.
+ This could be for libraries or other types of shared resources.
+ The `submodule` command has several sub-commands (`add`, `update`, `sync`, etc) for managing these resources.
+ 
+-This command is only mentioned and entirely covered in <<ch07-git-tools#_git_submodules>>.
++This command is only mentioned and entirely covered in <<ch07-git-tools#r_git_submodules>>.
+ 
+ === Inspection and Comparison
+ 
+-==== git show
+-
+ The `git show` command can show a Git object in a simple and human readable way.
+ Normally you would use this to show the information about a tag or a commit.
+ 
+-We first use it to show annotated tag information in <<ch02-git-basics-chapter#_annotated_tags>>.
++We first use it to show annotated tag information in <<ch02-git-basics#r_annotated_tags>>.
+ 
+-Later we use it quite a bit in <<ch07-git-tools#_revision_selection>> to show the commits that our various revision selections resolve to.
++Later we use it quite a bit in <<ch07-git-tools#r_revision_selection>> to show the commits that our various revision selections resolve to.
+ 
+-One of the more interesting things we do with `git show` is in <<ch07-git-tools#_manual_remerge>> to extract specific file contents of various stages during a merge conflict.
+-
+-==== git shortlog
++One of the more interesting things we do with `git show` is in <<ch07-git-tools#r_manual_remerge>> to extract specific file contents of various stages during a merge conflict.
+ 
+ The `git shortlog` command is used to summarize the output of `git log`.
+ It will take many of the same options that the `git log` command will but instead of listing out all of the commits it will present a summary of the commits grouped by author.
+ 
+-We showed how to use it to create a nice changelog in <<ch05-distributed-git#_the_shortlog>>.
+-
+-==== git describe
++We showed how to use it to create a nice changelog in <<ch05-distributed-git#r_the_shortlog>>.
+ 
+ The `git describe` command is used to take anything that resolves to a commit and produces a string that is somewhat human-readable and will not change.
+ It's a way to get a description of a commit that is as unambiguous as a commit SHA-1 but more understandable.
+ 
+-We use `git describe` in <<ch05-distributed-git#_build_number>> and <<ch05-distributed-git#_preparing_release>> to get a string to name our release file after.
+-
++We use `git describe` in <<ch05-distributed-git#r_build_number>> and <<ch05-distributed-git#r_preparing_release>> to get a string to name our release file after.
+ 
+ === Debugging
+ 
+ Git has a couple of commands that are used to help debug an issue in your code.
+ This ranges from figuring out where something was introduced to figuring out who introduced it.
+ 
+-==== git bisect
+-
+ The `git bisect` tool is an incredibly helpful debugging tool used to find which specific commit was the first one to introduce a bug or problem by doing an automatic binary search.
+ 
+-It is fully covered in <<ch07-git-tools#_binary_search>> and is only mentioned in that section.
+-
+-==== git blame
++It is fully covered in <<ch07-git-tools#r_binary_search>> and is only mentioned in that section.
+ 
+ The `git blame` command annotates the lines of any file with which commit was the last one to introduce a change to each line of the file and what person authored that commit.
+ This is helpful in order to find the person to ask for more information about a specific section of your code.
+ 
+-It is covered in <<ch07-git-tools#_file_annotation>> and is only mentioned in that section.
+-
+-==== git grep
++It is covered in <<ch07-git-tools#r_file_annotation>> and is only mentioned in that section.
+ 
+ The `git grep` command can help you find any string or regular expression in any of the files in your source code, even older versions of your project.
+ 
+-It is covered in <<ch07-git-tools#_git_grep>> and is only mentioned in that section.
++It is covered in <<ch07-git-tools#r_git_grep>> and is only mentioned in that section.
+ 
+ === Patching
+ 
+ A few commands in Git are centered around the concept of thinking of commits in terms of the changes they introduce, as though the commit series is a series of patches.
+ These commands help you manage your branches in this manner.
+ 
+-==== git cherry-pick
+-
+ The `git cherry-pick` command is used to take the change introduced in a single Git commit and try to re-introduce it as a new commit on the branch you're currently on.
+ This can be useful to only take one or two commits from a branch individually rather than merging in the branch which takes all the changes.
+ 
+-Cherry picking is described and demonstrated in <<ch05-distributed-git#_rebase_cherry_pick>>.
+-
+-==== git rebase
++Cherry picking is described and demonstrated in <<ch05-distributed-git#r_rebase_cherry_pick>>.
+ 
+ The `git rebase` command is basically an automated `cherry-pick`.
+ It determines a series of commits and then cherry-picks them one by one in the same order somewhere else.
+ 
+-Rebasing is covered in detail in <<ch03-git-branching#_rebasing>>, including covering the collaborative issues involved with rebasing branches that are already public.
+-
+-We use it in practice during an example of splitting your history into two separate repositories in <<ch07-git-tools#_replace>>, using the `--onto` flag as well.
++Rebasing is covered in detail in <<ch03-git-branching#r_rebasing>>, including covering the collaborative issues involved with rebasing branches that are already public.
+ 
+-We go through running into a merge conflict during rebasing in <<ch07-git-tools#ref_rerere>>.
++We use it in practice during an example of splitting your history into two separate repositories in <<ch07-git-tools#r_replace>>, using the `--onto` flag as well.
+ 
+-We also use it in an interactive scripting mode with the `-i` option in <<ch07-git-tools#_changing_multiple>>.
++We go through running into a merge conflict during rebasing in <<ch07-git-tools#r_rerere>>.
+ 
+-==== git revert
++We also use it in an interactive scripting mode with the `-i` option in <<ch07-git-tools#r_changing_multiple>>.
+ 
+ The `git revert` command is essentially a reverse `git cherry-pick`.
+ It creates a new commit that applies the exact opposite of the change introduced in the commit you're targeting, essentially undoing or reverting it.
+ 
+-We use this in <<ch07-git-tools#_reverse_commit>> to undo a merge commit.
++We use this in <<ch07-git-tools#r_reverse_commit>> to undo a merge commit.
+ 
+ === Email
+ 
+ Many Git projects, including Git itself, are entirely maintained over mailing lists.
+ Git has a number of tools built into it that help make this process easier, from generating patches you can easily email to applying those patches from an email box.
+ 
+-==== git apply
+-
+ The `git apply` command applies a patch created with the `git diff` or even GNU diff command.
+ It is similar to what the `patch` command might do with a few small differences.
+ 
+-We demonstrate using it and the circumstances in which you might do so in <<ch05-distributed-git#_patches_from_email>>.
+-
+-==== git am
++We demonstrate using it and the circumstances in which you might do so in <<ch05-distributed-git#r_patches_from_email>>.
+ 
+ The `git am` command is used to apply patches from an email inbox, specifically one that is mbox formatted.
+ This is useful for receiving patches over email and applying them to your project easily.
+ 
+-We covered usage and workflow around `git am` in <<ch05-distributed-git#_git_am>> including using the `--resolved`, `-i` and `-3` options.
++We covered usage and workflow around `git am` in <<ch05-distributed-git#r_git_am>> including using the `--resolved`, `-i` and `-3` options.
+ 
+-There are also a number of hooks you can use to help with the workflow around `git am` and they are all covered in <<ch08-customizing-git#_email_hooks>>.
++There are also a number of hooks you can use to help with the workflow around `git am` and they are all covered in <<ch08-customizing-git#r_email_hooks>>.
+ 
+-We also use it to apply patch formatted GitHub Pull Request changes in <<ch06-github#_email_notifications>>.
+-
+-==== git format-patch
++We also use it to apply patch formatted GitHub Pull Request changes in <<ch06-github#r_email_notifications>>.
+ 
+ The `git format-patch` command is used to generate a series of patches in mbox format that you can use to send to a mailing list properly formatted.
+ 
+-We go through an example of contributing to a project using the `git format-patch` tool in <<ch05-distributed-git#_project_over_email>>.
+-
+-==== git imap-send
++We go through an example of contributing to a project using the `git format-patch` tool in <<ch05-distributed-git#r_project_over_email>>.
+ 
+ The `git imap-send` command uploads a mailbox generated with `git format-patch` into an IMAP drafts folder.
+ 
+-We go through an example of contributing to a project by sending patches with the `git imap-send` tool in <<ch05-distributed-git#_project_over_email>>.
+-
+-==== git send-email
++We go through an example of contributing to a project by sending patches with the `git imap-send` tool in <<ch05-distributed-git#r_project_over_email>>.
+ 
+ The `git send-email` command is used to send patches that are generated with `git format-patch` over email.
+ 
+-We go through an example of contributing to a project by sending patches with the `git send-email` tool in <<ch05-distributed-git#_project_over_email>>.
+-
+-==== git request-pull
++We go through an example of contributing to a project by sending patches with the `git send-email` tool in <<ch05-distributed-git#r_project_over_email>>.
+ 
+ The `git request-pull` command is simply used to generate an example message body to email to someone.
+ If you have a branch on a public server and want to let someone know how to integrate those changes without sending the patches over email, you can run this command and send the output to the person you want to pull the changes in.
+ 
+-We demonstrate how to use `git request-pull` to generate a pull message in <<ch05-distributed-git#_public_project>>.
++We demonstrate how to use `git request-pull` to generate a pull message in <<ch05-distributed-git#r_public_project>>.
+ 
+ === External Systems
+ 
+ Git comes with a few commands to integrate with other version control systems.
+ 
+-==== git svn
+-
+ The `git svn` command is used to communicate with the Subversion version control system as a client.
+ This means you can use Git to checkout from and commit to a Subversion server.
+ 
+-This command is covered in depth in <<ch09-git-and-other-systems#_git_svn>>.
+-
+-==== git fast-import
++This command is covered in depth in <<ch09-git-and-other-scms#r_git_svn>>.
+ 
+ For other version control systems or importing from nearly any format, you can use `git fast-import` to quickly map the other format to something Git can easily record.
+ 
+-This command is covered in depth in <<ch09-git-and-other-systems#_custom_importer>>.
++This command is covered in depth in <<ch09-git-and-other-scms#r_custom_importer>>.
+ 
+ === Administration
+ 
+ If you're administering a Git repository or need to fix something in a big way, Git provides a number of administrative commands to help you out.
+ 
+-==== git gc
+-
+ The `git gc` command runs ``garbage collection'' on your repository, removing unnecessary files in your database and packing up the remaining files into a more efficient format.
+ 
+ This command normally runs in the background for you, though you can manually run it if you wish.
+-We go over some examples of this in <<ch10-git-internals#_git_gc>>.
+-
+-==== git fsck
++We go over some examples of this in <<ch10-git-internals#r_git_gc>>.
+ 
+ The `git fsck` command is used to check the internal database for problems or inconsistencies.
+ 
+-We only quickly use this once in <<ch10-git-internals#_data_recovery>> to search for dangling objects.
+-
+-==== git reflog
++We only quickly use this once in <<ch10-git-internals#r_data_recovery>> to search for dangling objects.
+ 
+ The `git reflog` command goes through a log of where all the heads of your branches have been as you work to find commits you may have lost through rewriting histories.
+ 
+-We cover this command mainly in <<ch07-git-tools#_git_reflog>>, where we show normal usage to and how to use `git log -g` to view the same information with `git log` output.
+-
+-We also go through a practical example of recovering such a lost branch in <<ch10-git-internals#_data_recovery>>.
++We cover this command mainly in <<ch07-git-tools#r_git_reflog>>, where we show normal usage to and how to use `git log -g` to view the same information with `git log` output.
+ 
+-==== git filter-branch
++We also go through a practical example of recovering such a lost branch in <<ch10-git-internals#r_data_recovery>>.
+ 
+ The `git filter-branch` command is used to rewrite loads of commits according to certain patterns, like removing a file everywhere or filtering the entire repository down to a single subdirectory for extracting a project.
+ 
+-In <<ch07-git-tools#_removing_file_every_commit>> we explain the command and explore several different options such as `--commit-filter`, `--subdirectory-filter` and `--tree-filter`.
+-
+-In <<ch09-git-and-other-systems#_git_p4>> we use it to fix up imported external repositories.
++In <<ch07-git-tools#r_removing_file_every_commit>> we explain the command and explore several different options such as `--commit-filter`, `--subdirectory-filter` and `--tree-filter`.
+ 
++In <<ch09-git-and-other-scms#r_git_p4>> and <<ch09-git-and-other-scms#r_git_tfs>> we use it to fix up imported external repositories.
+ 
+ === Plumbing Commands
+ 
+ There were also quite a number of lower level plumbing commands that we encountered in the book.
+ 
+-The first one we encounter is `ls-remote` in <<ch06-github#_pr_refs>> which we use to look at the raw references on the server.
++The first one we encounter is `ls-remote` in <<ch06-github#r_pr_refs>> which we use to look at the raw references on the server.
+ 
+-We use `ls-files` in <<ch07-git-tools#_manual_remerge>>, <<ch07-git-tools#ref_rerere>> and <<ch07-git-tools#_the_index>> to take a more raw look at what your staging area looks like.
++We use `ls-files` in <<ch07-git-tools#r_manual_remerge>>, <<ch07-git-tools#r_rerere>> and <<ch07-git-tools#r_the_index>> to take a more raw look at what your staging area looks like.
+ 
+-We also mention `rev-parse` in <<ch07-git-tools#_branch_references>> to take just about any string and turn it into an object SHA-1.
++We also mention `rev-parse` in <<ch07-git-tools#r_branch_references>> to take just about any string and turn it into an object SHA-1.
+ 
+ However, most of the low level plumbing commands we cover are in <<ch10-git-internals#ch10-git-internals>>, which is more or less what the chapter is focused on.
+ We tried to avoid use of them throughout most of the rest of the book.
+diff -au ../../git/progit2/progit2/LICENSE.asc /tmp/LICENSE.asc.tmp
+--- ../../git/progit2/progit2/LICENSE.asc	2020-06-28 16:44:50.900011670 +0900
++++ /tmp/LICENSE.asc.tmp	2020-10-25 09:24:25.552961813 +0900
+@@ -1,2 +0,0 @@
+-This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.
+-To view a copy of this license, visit https://creativecommons.org/licenses/by-nc-sa/3.0 or send a letter to Creative Commons, PO Box 1866, Mountain View, CA 94042, USA.
+diff -au ../../git/progit2/progit2/README.asc /tmp/README.asc.tmp
+--- ../../git/progit2/progit2/README.asc	2020-09-07 09:33:11.246683703 +0900
++++ /tmp/README.asc.tmp	2020-10-25 09:24:25.563962332 +0900
+@@ -1,22 +1,51 @@
++= Pro Git 第2版 日本語翻訳
++
++このリポジトリを使って、Pro Git第2版の日本語翻訳作業を進めています。
++
++- 翻訳を手伝ってみたい
++- 書いてある技術的内容or日本語が間違ってるんだけど
++- どうやって電子書籍データを生成してるんですか？
++
++などなど、興味を持っていただいた方を歓迎しています。何かありましたら https://github.com/progit/progit2-ja/issues/[Issue] をたてていただくか、メンテナの https://twitter.com/harupong[@harupong] までご連絡いただければ幸いです。
++
++== 翻訳作業のお約束
++
++翻訳のお手伝いは大歓迎です。以下の2点を踏まえ、ぜひご協力いただければと思っています。
++
++1. 作業を始めるときは意思表示をしてください
++1. 既訳を尊重してください
++
++具体的な作業手順など、詳しいことは link:TRANSLATION_NOTES.asc[TRANSLATION NOTES] を確認してください。
++
++''''''''''''''''''''''''''
++（Below is the translation of original README.asc in English. 以下は英語READMEの翻訳です。）
++
+ = Pro Git, Second Edition
+ 
+ Welcome to the second edition of the Pro Git book.
+ 
+-You can find this book online at: https://git-scm.com/book
++You can find this book online at: http://git-scm.com/book
+ 
+ Like the first edition, the second edition of Pro Git is open source under a Creative Commons license.
+ 
+ A couple of things have changed since open sourcing the first edition.
+-For one, we've moved from Markdown to the amazing AsciiDoc format for the text of the book; here's an https://asciidoctor.org/docs/asciidoc-syntax-quick-reference/[AsciiDoc quick reference].
++For one, we've moved from Markdown to the amazing Asciidoc format for the text of the book.
++We've also moved to using O'Reilly's https://atlas.oreilly.com[Atlas platform] for generating continuous builds of the book so all major formats are always available in every language.
+ 
+ We've also moved to keeping the translations in separate repositories rather than subdirectories of the English repository.
+-See link:TRANSLATING.md[the translating document] for more information.
++See link:CONTRIBUTING.md[the Contributing document] for more information.
+ 
+ == How To Generate the Book
+ 
+-You can generate the e-book files manually with Asciidoctor.
+-We used to be able to build .mobi files (Kindle), but cannot do so now, see #1496 for more information.
+-If you run the following you _may_ actually get HTML, Epub and PDF output files:
++There are two ways to generate e-book content from this source code.
++
++The easiest way is simply to let us do it.
++A robot is standing by to look for new work on the main branch and automatically build it for everyone.
++
++You can find the current builds on http://git-scm.com/book[] and more information about the builds available at https://progit.org[].
++
++The other way to generate e-book files is to do so manually with Asciidoctor.
++If you run the following you _may_ actually get HTML, Epub, Mobi and PDF output files:
+ 
+ ----
+ $ bundle install
+@@ -25,17 +54,20 @@
+  -- HTML output at progit.html
+ Converting to EPub...
+  -- Epub output at progit.epub
++Converting to Mobi (kf8)...
++ -- Mobi output at progit.mobi
+ Converting to PDF...
+- -- PDF output at progit.pdf
++ -- PDF  output at progit.pdf
+ ----
+ 
++This uses the `asciidoctor`, `asciidoctor-pdf` and `asciidoctor-epub` projects.
++
+ == Signaling an Issue
+ 
+ Before signaling an issue, please check that there isn't already a similar one in the bug tracking system.
+ 
+-Also, if this issue has been spotted on the git-scm.com site, please cross-check that it is still present in this repo.
+-The issue may have already been corrected, but the changes have not been deployed yet.
++Also, if this issue has been spotted on the git-scm.com site, please cross-check that it is still present in the pdf version. The issue may have already been corrected, but the changes have not been deployed yet.
+ 
+ == Contributing
+ 
+-If you'd like to help out by making a change, take a look at the link:CONTRIBUTING.md[contributor's guide].
++If you'd like to help out by making a change or contributing a translation, take a look at the link:CONTRIBUTING.md[contributor's guide].
+diff -au ../../git/progit2/progit2/TRANSLATION_NOTES.asc /tmp/TRANSLATION_NOTES.asc.tmp
+--- ../../git/progit2/progit2/TRANSLATION_NOTES.asc	2020-06-28 16:44:50.919014468 +0900
++++ /tmp/TRANSLATION_NOTES.asc.tmp	2020-10-25 09:24:25.577962992 +0900
+@@ -1,11 +0,0 @@
+-== Translation Notes
+-
+-After forking this repository to translate the work, this file is where the notes for coordinating the translation work would go.
+-Things like standardizing on words and expressions so that the work is consistent or notes on how the contributing process is to be handled.
+-
+-As a translation maintainer, also feel free to modify or completely rewrite the README file to contain instructions specific to your translation.
+-
+-=== Translation Status
+-
+-As the work is translated, please update the `status.json` file to indicate the rough percentage complete each file is.
+-This will be shown on various pages to let people know how much work is left to be done.
+diff -au ../../git/progit2/progit2/book/01-introduction/sections/about-version-control.asc /tmp/book/01-introduction/sections/about-version-control.asc.tmp
+--- ../../git/progit2/progit2/book/01-introduction/sections/about-version-control.asc	2020-07-04 16:36:46.718685392 +0900
++++ /tmp/book/01-introduction/sections/about-version-control.asc.tmp	2020-10-25 09:24:25.587963463 +0900
+@@ -1,60 +1,57 @@
+ === About Version Control
+ 
+-(((version control)))
+-What is ``version control'', and why should you care?
++What is "version control", and why should you care?
+ Version control is a system that records changes to a file or set of files over time so that you can recall specific versions later.
+-For the examples in this book, you will use software source code as the files being version controlled, though in reality you can do this with nearly any type of file on a computer.
++For the examples in this book you will use software source code as the files being version controlled, though in reality you can do this with nearly any type of file on a computer.
+ 
+ If you are a graphic or web designer and want to keep every version of an image or layout (which you would most certainly want to), a Version Control System (VCS) is a very wise thing to use.
+-It allows you to revert selected files back to a previous state, revert the entire project back to a previous state, compare changes over time, see who last modified something that might be causing a problem, who introduced an issue and when, and more.
++It allows you to revert files back to a previous state, revert the entire project back to a previous state, compare changes over time, see who last modified something that might be causing a problem, who introduced an issue and when, and more.
+ Using a VCS also generally means that if you screw things up or lose files, you can easily recover.
+ In addition, you get all this for very little overhead.
+ 
+ ==== Local Version Control Systems
+ 
+-(((version control,local)))
+ Many people's version-control method of choice is to copy files into another directory (perhaps a time-stamped directory, if they're clever).
+ This approach is very common because it is so simple, but it is also incredibly error prone.
+ It is easy to forget which directory you're in and accidentally write to the wrong file or copy over files you don't mean to.
+ 
+ To deal with this issue, programmers long ago developed local VCSs that had a simple database that kept all the changes to files under revision control.
+ 
+-.Local version control
++.Local version control.
+ image::images/local.png[Local version control diagram]
+ 
+-One of the most popular VCS tools was a system called RCS, which is still distributed with many computers today.
+-https://www.gnu.org/software/rcs/[RCS] works by keeping patch sets (that is, the differences between files) in a special format on disk; it can then re-create what any file looked like at any point in time by adding up all the patches.
++One of the more popular VCS tools was a system called RCS, which is still distributed with many computers today.
++Even the popular Mac OS X operating system includes the `rcs` command when you install the Developer Tools.
++RCS works by keeping patch sets (that is, the differences between files) in a special format on disk; it can then re-create what any file looked like at any point in time by adding up all the patches.
+ 
+ ==== Centralized Version Control Systems
+ 
+-(((version control,centralized)))
+ The next major issue that people encounter is that they need to collaborate with developers on other systems.
+ To deal with this problem, Centralized Version Control Systems (CVCSs) were developed.
+-These systems (such as CVS, Subversion, and Perforce) have a single server that contains all the versioned files, and a number of clients that check out files from that central place. (((CVS)))(((Subversion)))(((Perforce)))
++These systems, such as CVS, Subversion, and Perforce, have a single server that contains all the versioned files, and a number of clients that check out files from that central place. (((CVS)))(((Subversion)))(((Perforce)))
+ For many years, this has been the standard for version control.
+ 
+-.Centralized version control
++.Centralized version control.
+ image::images/centralized.png[Centralized version control diagram]
+ 
+ This setup offers many advantages, especially over local VCSs.
+ For example, everyone knows to a certain degree what everyone else on the project is doing.
+-Administrators have fine-grained control over who can do what, and it's far easier to administer a CVCS than it is to deal with local databases on every client.
++Administrators have fine-grained control over who can do what; and it's far easier to administer a CVCS than it is to deal with local databases on every client.
+ 
+ However, this setup also has some serious downsides.
+ The most obvious is the single point of failure that the centralized server represents.
+ If that server goes down for an hour, then during that hour nobody can collaborate at all or save versioned changes to anything they're working on.
+-If the hard disk the central database is on becomes corrupted, and proper backups haven't been kept, you lose absolutely everything -- the entire history of the project except whatever single snapshots people happen to have on their local machines.
+-Local VCS systems suffer from this same problem -- whenever you have the entire history of the project in a single place, you risk losing everything.
++If the hard disk the central database is on becomes corrupted, and proper backups haven't been kept, you lose absolutely everything – the entire history of the project except whatever single snapshots people happen to have on their local machines.
++Local VCS systems suffer from this same problem – whenever you have the entire history of the project in a single place, you risk losing everything.
+ 
+ ==== Distributed Version Control Systems
+ 
+-(((version control,distributed)))
+ This is where Distributed Version Control Systems (DVCSs) step in.
+-In a DVCS (such as Git, Mercurial, Bazaar or Darcs), clients don't just check out the latest snapshot of the files; rather, they fully mirror the repository, including its full history.
+-Thus, if any server dies, and these systems were collaborating via that server, any of the client repositories can be copied back up to the server to restore it.
++In a DVCS (such as Git, Mercurial, Bazaar or Darcs), clients don't just check out the latest snapshot of the files: they fully mirror the repository.
++Thus if any server dies, and these systems were collaborating via it, any of the client repositories can be copied back up to the server to restore it.
+ Every clone is really a full backup of all the data.
+ 
+-.Distributed version control
++.Distributed version control.
+ image::images/distributed.png[Distributed version control diagram]
+ 
+ Furthermore, many of these systems deal pretty well with having several remote repositories they can work with, so you can collaborate with different groups of people in different ways simultaneously within the same project.
+diff -au ../../git/progit2/progit2/book/01-introduction/sections/command-line.asc /tmp/book/01-introduction/sections/command-line.asc.tmp
+--- ../../git/progit2/progit2/book/01-introduction/sections/command-line.asc	2020-06-28 16:44:50.920014615 +0900
++++ /tmp/book/01-introduction/sections/command-line.asc.tmp	2020-10-25 09:24:25.591963652 +0900
+@@ -1,11 +1,11 @@
+ === The Command Line
+ 
+ There are a lot of different ways to use Git.
+-There are the original command-line tools, and there are many graphical user interfaces of varying capabilities.
++There are the original command line tools, and there are many graphical user interfaces of varying capabilities.
+ For this book, we will be using Git on the command line.
+-For one, the command line is the only place you can run _all_ Git commands -- most of the GUIs implement only a partial subset of Git functionality for simplicity.
+-If you know how to run the command-line version, you can probably also figure out how to run the GUI version, while the opposite is not necessarily true.
++For one, the command line is the only place you can run *all* Git commands – most of the GUIs only implement some subset of Git functionality for simplicity.
++If you know how to run the command line version, you can probably also figure out how to run the GUI version, while the opposite is not necessarily true.
+ Also, while your choice of graphical client is a matter of personal taste, _all_ users will have the command-line tools installed and available.
+ 
+-So we will expect you to know how to open Terminal in macOS or Command Prompt or PowerShell in Windows.
++So we will expect you to know how to open Terminal in Mac or Command Prompt or Powershell in Windows.
+ If you don't know what we're talking about here, you may need to stop and research that quickly so that you can follow the rest of the examples and descriptions in this book.
+diff -au ../../git/progit2/progit2/book/01-introduction/sections/first-time-setup.asc /tmp/book/01-introduction/sections/first-time-setup.asc.tmp
+--- ../../git/progit2/progit2/book/01-introduction/sections/first-time-setup.asc	2020-08-10 10:02:15.168231103 +0900
++++ /tmp/book/01-introduction/sections/first-time-setup.asc.tmp	2020-10-25 09:24:25.597963934 +0900
+@@ -1,4 +1,4 @@
+-[[_first_time]]
++[[r_first_time]]
+ === First-Time Git Setup
+ 
+ Now that you have Git on your system, you'll want to do a few things to customize your Git environment.
+@@ -8,129 +8,58 @@
+ Git comes with a tool called `git config` that lets you get and set configuration variables that control all aspects of how Git looks and operates.(((git commands, config)))
+ These variables can be stored in three different places:
+ 
+-1. `[path]/etc/gitconfig` file: Contains values applied to every user on the system and all their repositories.
++1. `/etc/gitconfig` file: Contains values for every user on the system and all their repositories.
+   If you pass the option `--system` to `git config`, it reads and writes from this file specifically.
+-  Because this is a system configuration file, you would need administrative or superuser privilege to make changes to it.
+-2. `~/.gitconfig` or `~/.config/git/config` file: Values specific personally to you, the user.
+-  You can make Git read and write to this file specifically by passing the `--global` option, and this affects _all_ of the repositories you work with on your system.
++2. `~/.gitconfig` or `~/.config/git/config` file: Specific to your user.
++  You can make Git read and write to this file specifically by passing the `--global` option.
+ 3. `config` file in the Git directory (that is, `.git/config`) of whatever repository you're currently using: Specific to that single repository.
+-  You can force Git to read from and write to this file with the `--local` option, but that is in fact the default.
+-  Unsurprisingly, you need to be located somewhere in a Git repository for this option to work properly.
+ 
+-Each level overrides values in the previous level, so values in `.git/config` trump those in `[path]/etc/gitconfig`.
++Each level overrides values in the previous level, so values in `.git/config` trump those in `/etc/gitconfig`.
+ 
+ On Windows systems, Git looks for the `.gitconfig` file in the `$HOME` directory (`C:\Users\$USER` for most people).
+-It also still looks for `[path]/etc/gitconfig`, although it's relative to the MSys root, which is wherever you decide to install Git on your Windows system when you run the installer.
+-If you are using version 2.x or later of Git for Windows, there is also a system-level config file at
++It also still looks for `/etc/gitconfig`, although it's relative to the MSys root, which is wherever you decide to install Git on your Windows system when you run the installer.
++If you are using Git for Windows 2.x or later, there is also a system-level config file at
+ `C:\Documents and Settings\All Users\Application Data\Git\config` on Windows XP, and in `C:\ProgramData\Git\config` on Windows Vista and newer.
+ This config file can only be changed by `git config -f <file>` as an admin.
+ 
+-You can view all of your settings and where they are coming from using:
+-
+-[source,console]
+-----
+-$ git config --list --show-origin
+-----
+-
+ ==== Your Identity
+ 
+ The first thing you should do when you install Git is to set your user name and email address.
+ This is important because every Git commit uses this information, and it's immutably baked into the commits you start creating:
+ 
+-[source,console]
+-----
+-$ git config --global user.name "John Doe"
+-$ git config --global user.email [e-mail]
+-----
+-
+ Again, you need to do this only once if you pass the `--global` option, because then Git will always use that information for anything you do on that system.
++<<<<<<< HEAD
+ If you want to override this with a different name or email address for specific projects, you can run the command without the `--global` option when you're in that project.
+ 
+ Many of the GUI tools will help you do this when you first run them.
+ 
+-[[_editor]]
+ ==== Your Editor
+ 
+ Now that your identity is set up, you can configure the default text editor that will be used when Git needs you to type in a message.
+ If not configured, Git uses your system's default editor.
+-
+ If you want to use a different text editor, such as Emacs, you can do the following:
+ 
+-[source,console]
+-----
+-$ git config --global core.editor emacs
+-----
+-
+-On a Windows system, if you want to use a different text editor, you must specify the full path to its executable file.
+-This can be different depending on how your editor is packaged.
+-
+-In the case of Notepad++, a popular programming editor, you are likely to want to use the 32-bit version, since at the time of writing the 64-bit version doesn't support all plug-ins.
+-If you are on a 32-bit Windows system, or you have a 64-bit editor on a 64-bit system, you'll type something like this:
+-
+-[source,console]
+-----
+-$ git config --global core.editor "'C:/Program Files/Notepad++/notepad++.exe' -multiInst -notabbar -nosession -noPlugin"
+-----
++While on a Windows system, if you want to use a different text editor, such as Notepad++, you can do the following:
++
++On a x86 system
++
++On a x64 system
+ 
+-[NOTE]
+ ====
+-Vim, Emacs and Notepad++ are popular text editors often used by developers on Unix-based systems like Linux and macOS or a Windows system.
+-If you are using another editor, or a 32-bit version, please find specific instructions for how to set up your favorite editor with Git in <<C-git-commands#_core_editor>>.
++Vim, Emacs and Notepad++ are popular text editors often used by developers on Unix based systems like Linux and OS X or a Windows system.
++If you are not familiar with either of these editors, you may need to search for specific instructions for how to set up your favorite editor with Git.
+ ====
+ 
+-[WARNING]
+ ====
+-You may find, if you don't setup your editor like this, you get into a really confusing state when Git attempts to launch it.
+-An example on a Windows system may include a prematurely terminated Git operation during a Git initiated edit.
++You may find, if you don't setup an editor like this, you will likely get into a really confusing state when they are launched.
++Such example on a Windows system may include a prematurely terminated Git operation during a Git initiated edit.
+ ====
+ 
+-==== Your default branch name
+-
+-By default Git will create a branch called _master_ when you create a new repository with `git init`.
+-From Git version 2.28 onwards, you can set a different name for the initial branch.
+-
+-To set _main_ as the default branch name do:
+-
+-[source,console]
+-----
+-$ git config --global init.defaultBranch main
+-----
+-
+ ==== Checking Your Settings
+ 
+-If you want to check your configuration settings, you can use the `git config --list` command to list all the settings Git can find at that point:
++If you want to check your settings, you can use the `git config --list` command to list all the settings Git can find at that point:
+ 
+-[source,console]
+-----
+-$ git config --list
+-user.name=John Doe
+-user.email=[e-mail]
+-color.status=auto
+-color.branch=auto
+-color.interactive=auto
+-color.diff=auto
+-...
+-----
+-
+-You may see keys more than once, because Git reads the same key from different files (`[path]/etc/gitconfig` and `~/.gitconfig`, for example).
++You may see keys more than once, because Git reads the same key from different files (`/etc/gitconfig` and `~/.gitconfig`, for example).
+ In this case, Git uses the last value for each unique key it sees.
+ 
+ You can also check what Git thinks a specific key's value is by typing `git config <key>`:(((git commands, config)))
+-
+-[source,console]
+-----
+-$ git config user.name
+-John Doe
+-----
+-
+-[NOTE]
+-====
+-Since Git might read the same configuration variable value from more than one file, it's possible that you have an unexpected value for one of these values and you don't know why.
+-In cases like that, you can query Git as to the _origin_ for that value, and it will tell you which configuration file had the final say in setting that value:
+-
+-[source,console]
+-----
+-$ git config --show-origin rerere.autoUpdate
+-file:/home/johndoe/.gitconfig	false
+-----
+-====
+diff -au ../../git/progit2/progit2/book/01-introduction/sections/help.asc /tmp/book/01-introduction/sections/help.asc.tmp
+--- ../../git/progit2/progit2/book/01-introduction/sections/help.asc	2020-07-04 16:36:46.718685392 +0900
++++ /tmp/book/01-introduction/sections/help.asc.tmp	2020-10-25 09:24:25.601964123 +0900
+@@ -1,48 +1,10 @@
+-[[_git_help]]
++[[r_git_help]]
+ === Getting Help
+ 
+-If you ever need help while using Git, there are three equivalent ways to get the comprehensive manual page (manpage) help for any of the Git commands:
++If you ever need help while using Git, there are three ways to get the manual page (manpage) help for any of the Git commands:
+ 
+-[source,console]
+-----
+-$ git help <verb>
+-$ git <verb> --help
+-$ man git-<verb>
+-----
+-
+-For example, you can get the manpage help for the `git config` command by running this:(((git commands, help)))
+-
+-[source,console]
+-----
+-$ git help config
+-----
++For example, you can get the manpage help for the config command by running(((git commands, help)))
+ 
+ These commands are nice because you can access them anywhere, even offline.
+-If the manpages and this book aren't enough and you need in-person help, you can try the `#git` or `#github` channel on the Freenode IRC server, which can be found at https://freenode.net[].
++If the manpages and this book aren't enough and you need in-person help, you can try the `#git` or `#github` channel on the Freenode IRC server (irc.freenode.net).
+ These channels are regularly filled with hundreds of people who are all very knowledgeable about Git and are often willing to help.(((IRC)))
+-
+-In addition, if you don't need the full-blown manpage help, but just need a quick refresher on the available options for a Git command, you can ask for the more concise ``help'' output with the `-h` option, as in:
+-
+-[source,console]
+-----
+-$ git add -h
+-usage: git add [<options>] [--] <pathspec>...
+-
+-    -n, --dry-run         dry run
+-    -v, --verbose         be verbose
+-
+-    -i, --interactive     interactive picking
+-    -p, --patch           select hunks interactively
+-    -e, --edit            edit current diff and apply
+-    -f, --force           allow adding otherwise ignored files
+-    -u, --update          update tracked files
+-    --renormalize         renormalize EOL of tracked files (implies -u)
+-    -N, --intent-to-add   record only the fact that the path will be added later
+-    -A, --all             add changes from all tracked and untracked files
+-    --ignore-removal      ignore paths removed in the working tree (same as --no-all)
+-    --refresh             don't add, only refresh the index
+-    --ignore-errors       just skip files which cannot be added because of errors
+-    --ignore-missing      check if - even missing - files are ignored in dry run
+-    --chmod (+|-)x        override the executable bit of the listed files
+-----
+-
+diff -au ../../git/progit2/progit2/book/01-introduction/sections/history.asc /tmp/book/01-introduction/sections/history.asc.tmp
+--- ../../git/progit2/progit2/book/01-introduction/sections/history.asc	2020-06-28 16:44:50.921014763 +0900
++++ /tmp/book/01-introduction/sections/history.asc.tmp	2020-10-25 09:24:25.607964406 +0900
+@@ -17,4 +17,4 @@
+ *  Able to handle large projects like the Linux kernel efficiently (speed and data size)
+ 
+ Since its birth in 2005, Git has evolved and matured to be easy to use and yet retain these initial qualities.
+-It's amazingly fast, it's very efficient with large projects, and it has an incredible branching system for non-linear development (See <<ch03-git-branching#ch03-git-branching>>).
++It's incredibly fast, it's very efficient with large projects, and it has an incredible branching system for non-linear development (See <<ch03-git-branching#ch03-git-branching>>).
+diff -au ../../git/progit2/progit2/book/01-introduction/sections/installing.asc /tmp/book/01-introduction/sections/installing.asc.tmp
+--- ../../git/progit2/progit2/book/01-introduction/sections/installing.asc	2020-07-04 16:36:46.718685392 +0900
++++ /tmp/book/01-introduction/sections/installing.asc.tmp	2020-10-25 09:24:25.611964594 +0900
+@@ -4,144 +4,69 @@
+ Even if it's already installed, it's probably a good idea to update to the latest version.
+ You can either install it as a package or via another installer, or download the source code and compile it yourself.
+ 
+-[NOTE]
+ ====
+-This book was written using Git version *2.8.0*.
++This book was written using Git version *2.0.0*.
+ Though most of the commands we use should work even in ancient versions of Git, some of them might not or might act slightly differently if you're using an older version.
+-Since Git is quite excellent at preserving backwards compatibility, any version after 2.8 should work just fine.
++Since Git is quite excellent at preserving backwards compatibility, any version after 2.0 should work just fine.
+ ====
+ 
+ ==== Installing on Linux
+ 
+-(((Linux, installing)))
+-If you want to install the basic Git tools on Linux via a binary installer, you can generally do so through the package management tool that comes with your distribution.
+-If you're on Fedora (or any closely-related RPM-based distribution, such as RHEL or CentOS), you can use `dnf`:
++If you want to install the basic Git tools on Linux via a binary installer, you can generally do so through the basic package-management tool that comes with your distribution.
++If you're on Fedora for example, you can use yum:
+ 
+-[source,console]
+-----
+-$ sudo dnf install git-all
+-----
++If you're on a Debian-based distribution like Ubuntu, try apt-get:
+ 
+-If you're on a Debian-based distribution, such as Ubuntu, try `apt`:
++For more options, there are instructions for installing on several different Unix flavors on the Git website, at http://git-scm.com/download/linux[].
+ 
+-[source,console]
+-----
+-$ sudo apt install git-all
+-----
++==== Installing on Mac
+ 
+-For more options, there are instructions for installing on several different Unix distributions on the Git website, at https://git-scm.com/download/linux[].
+-
+-==== Installing on macOS
+-
+-(((macOS, installing)))
+ There are several ways to install Git on a Mac.
+ The easiest is probably to install the Xcode Command Line Tools.(((Xcode)))
+-On Mavericks (10.9) or above you can do this simply by trying to run `git` from the Terminal the very first time.
+-
+-[source,console]
+-----
+-$ git --version
+-----
+-
++On Mavericks (10.9) or above you can do this simply by trying to run 'git' from the Terminal the very first time.
+ If you don't have it installed already, it will prompt you to install it.
+ 
+ If you want a more up to date version, you can also install it via a binary installer.
+-A macOS Git installer is maintained and available for download at the Git website, at https://git-scm.com/download/mac[].
++An OSX Git installer is maintained and available for download at the Git website, at http://git-scm.com/download/mac[].
+ 
+-.Git macOS Installer
+-image::images/git-osx-installer.png[Git macOS installer]
++.Git OS X Installer.
++image::images/git-osx-installer.png[Git OS X installer.]
+ 
+-You can also install it as part of the GitHub for macOS install.
++You can also install it as part of the GitHub for Mac install.
+ Their GUI Git tool has an option to install command line tools as well.
+-You can download that tool from the GitHub for macOS website, at https://desktop.github.com[].
++You can download that tool from the GitHub for Mac website, at http://mac.github.com[].
+ 
+ ==== Installing on Windows
+ 
+ There are also a few ways to install Git on Windows.(((Windows, installing)))
+ The most official build is available for download on the Git website.
+-Just go to https://git-scm.com/download/win[] and the download will start automatically.
+-Note that this is a project called Git for Windows, which is separate from Git itself; for more information on it, go to https://gitforwindows.org[].
+-
+-To get an automated installation you can use the https://chocolatey.org/packages/git[Git Chocolatey package].
+-Note that the Chocolatey package is community maintained.
++Just go to http://git-scm.com/download/win[] and the download will start automatically.
++Note that this is a project called Git for Windows, which is separate from Git itself; for more information on it, go to https://git-for-windows.github.io/[].
+ 
+-Another easy way to get Git installed is by installing GitHub Desktop.
++Another easy way to get Git installed is by installing GitHub for Windows.
+ The installer includes a command line version of Git as well as the GUI.
+-It also works well with PowerShell, and sets up solid credential caching and sane CRLF settings.(((PowerShell)))(((CRLF)))(((credential caching)))
++It also works well with Powershell, and sets up solid credential caching and sane CRLF settings.(((Powershell)))(((CRLF)))(((credential caching)))
+ We'll learn more about those things a little later, but suffice it to say they're things you want.
+-You can download this from the https://desktop.github.com[GitHub Desktop website].
++You can download this from the GitHub for Windows website, at http://windows.github.com[].
+ 
+ ==== Installing from Source
+ 
+ Some people may instead find it useful to install Git from source, because you'll get the most recent version.
+ The binary installers tend to be a bit behind, though as Git has matured in recent years, this has made less of a difference.
+ 
+-If you do want to install Git from source, you need to have the following libraries that Git depends on: autotools, curl, zlib, openssl, expat, and libiconv.
+-For example, if you're on a system that has `dnf` (such as Fedora) or `apt-get` (such as a Debian-based system), you can use one of these commands to install the minimal dependencies for compiling and installing the Git binaries:
++If you do want to install Git from source, you need to have the following libraries that Git depends on: curl, zlib, openssl, expat, and libiconv.
++For example, if you're on a system that has yum (such as Fedora) or apt-get (such as a Debian based system), you can use one of these commands to install the minimal dependencies for compiling and installing the Git binaries:
+ 
+-[source,console]
+-----
+-$ sudo dnf install dh-autoreconf curl-devel expat-devel gettext-devel \
+-  openssl-devel perl-devel zlib-devel
+-$ sudo apt-get install dh-autoreconf libcurl4-gnutls-dev libexpat1-dev \
+-  gettext libz-dev libssl-dev
+-----
+-
+-In order to be able to add the documentation in various formats (doc, html, info), these additional dependencies are required:
+-
+-[source,console]
+-----
+-$ sudo dnf install asciidoc xmlto docbook2X
+-$ sudo apt-get install asciidoc xmlto docbook2x
+-----
++In order to be able to add the documentation in various formats (doc, html, info), these additional dependencies are required (Note: users of RHEL and RHEL-derivatives like CentOS and Scientific Linux will have to https://fedoraproject.org/wiki/EPEL#How_can_I_use_these_extra_packages.3F[enable the EPEL repository] to download the `docbook2X` package):
+ 
+-[NOTE]
+-====
+-Users of RHEL and RHEL-derivatives like CentOS and Scientific Linux will have to https://fedoraproject.org/wiki/EPEL#How_can_I_use_these_extra_packages.3F[enable the EPEL repository] to download the `docbook2X` package.
+-====
+-
+-If you're using a Debian-based distribution (Debian/Ubuntu/Ubuntu-derivatives), you also need the `install-info` package:
+-
+-[source,console]
+-----
+-$ sudo apt-get install install-info
+-----
+-
+-If you're using a RPM-based distribution (Fedora/RHEL/RHEL-derivatives), you also need the `getopt` package (which is already installed on a Debian-based distro):
+-
+-[source,console]
+-----
+-$ sudo dnf install getopt
+-----
+-
+-Additionally, if you're using Fedora/RHEL/RHEL-derivatives, you need to do this:
+-
+-[source,console]
+-----
+-$ sudo ln -s /usr/bin/db2x_docbook2texi /usr/bin/docbook2x-texi
+-----
++Additionally, if you're using Fedora/RHEL/RHEL-derivatives, you need to do this
+ 
+ due to binary name differences.
+ 
+ When you have all the necessary dependencies, you can go ahead and grab the latest tagged release tarball from several places.
+-You can get it via the kernel.org site, at https://www.kernel.org/pub/software/scm/git[], or the mirror on the GitHub website, at https://github.com/git/git/releases[].
++You can get it via the Kernel.org site, at https://www.kernel.org/pub/software/scm/git[], or the mirror on the GitHub web site, at https://github.com/git/git/releases[].
+ It's generally a little clearer what the latest version is on the GitHub page, but the kernel.org page also has release signatures if you want to verify your download.
+ 
+ Then, compile and install:
+ 
+-[source,console]
+-----
+-$ tar -zxf git-2.8.0.tar.gz
+-$ cd git-2.8.0
+-$ make configure
+-$ ./configure --prefix=/usr
+-$ make all doc info
+-$ sudo make install install-doc install-html install-info
+-----
+-
+ After this is done, you can also get Git via Git itself for updates:
+-
+-[source,console]
+-----
+-$ git clone git://git.kernel.org/pub/scm/git/git.git
+-----
+Warning: file not found: ../../git/progit2/progit2-ja/book/01-introduction/sections/what-is-git.asc
+diff -au ../../git/progit2/progit2/book/02-git-basics/sections/aliases.asc /tmp/book/02-git-basics/sections/aliases.asc.tmp
+--- ../../git/progit2/progit2/book/02-git-basics/sections/aliases.asc	2020-07-03 19:43:27.508489967 +0900
++++ /tmp/book/02-git-basics/sections/aliases.asc.tmp	2020-10-25 09:24:25.617964877 +0900
+@@ -1,70 +1,28 @@
+-[[_git_aliases]]
++[[r_git_aliases]]
+ === Git Aliases
+ 
+-(((aliases)))
+-Before we move on to the next chapter, we want to introduce a feature that can make your Git experience simpler, easier, and more familiar: aliases.
+-For clarity's sake, we won't be using them anywhere else in this book, but if you go on to use Git with any regularity, aliases are something you should know about.
++Before we finish this chapter on basic Git, there's just one little tip that can make your Git experience simpler, easier, and more familiar: aliases.
++We won't refer to them or assume you've used them later in the book, but you should probably know how to use them.
+ 
+ Git doesn't automatically infer your command if you type it in partially.
+ If you don't want to type the entire text of each of the Git commands, you can easily set up an alias for each command using `git config`.(((git commands, config)))
+ Here are a couple of examples you may want to set up:
+ 
+-[source,console]
+-----
+-$ git config --global alias.co checkout
+-$ git config --global alias.br branch
+-$ git config --global alias.ci commit
+-$ git config --global alias.st status
+-----
+-
+ This means that, for example, instead of typing `git commit`, you just need to type `git ci`.
+ As you go on using Git, you'll probably use other commands frequently as well; don't hesitate to create new aliases.
+ 
+ This technique can also be very useful in creating commands that you think should exist.
+ For example, to correct the usability problem you encountered with unstaging a file, you can add your own unstage alias to Git:
+ 
+-[source,console]
+-----
+-$ git config --global alias.unstage 'reset HEAD --'
+-----
+-
+ This makes the following two commands equivalent:
+ 
+-[source,console]
+-----
+-$ git unstage fileA
+-$ git reset HEAD -- fileA
+-----
+-
+ This seems a bit clearer.
+ It's also common to add a `last` command, like this:
+ 
+-[source,console]
+-----
+-$ git config --global alias.last 'log -1 HEAD'
+-----
+-
+ This way, you can see the last commit easily:
+ 
+-[source,console]
+-----
+-$ git last
+-commit 66938dae3329c7aebe598c2246a8e6af90d04646
+-Author: Josh Goebel <[e-mail]>
+-Date:   Tue Aug 26 19:48:51 2008 +0800
+-
+-    Test for current head
+-
+-    Signed-off-by: Scott Chacon <[e-mail]>
+-----
+-
+ As you can tell, Git simply replaces the new command with whatever you alias it for.
+ However, maybe you want to run an external command, rather than a Git subcommand.
+ In that case, you start the command with a `!` character.
+ This is useful if you write your own tools that work with a Git repository.
+ We can demonstrate by aliasing `git visual` to run `gitk`:
+-
+-[source,console]
+-----
+-$ git config --global alias.visual '!gitk'
+-----
+diff -au ../../git/progit2/progit2/book/02-git-basics/sections/getting-a-repository.asc /tmp/book/02-git-basics/sections/getting-a-repository.asc.tmp
+--- ../../git/progit2/progit2/book/02-git-basics/sections/getting-a-repository.asc	2020-07-01 10:48:37.610009640 +0900
++++ /tmp/book/02-git-basics/sections/getting-a-repository.asc.tmp	2020-10-25 09:24:25.621965066 +0900
+@@ -1,87 +1,41 @@
+-[[_getting_a_repo]]
++[[r_getting_a_repo]]
+ === Getting a Git Repository
+ 
+-You typically obtain a Git repository in one of two ways:
+-
+-1. You can take a local directory that is currently not under version control, and turn it into a Git repository, or
+-2. You can _clone_ an existing Git repository from elsewhere.
+-
+-In either case, you end up with a Git repository on your local machine, ready for work.
++You can get a Git project using two main approaches.
++The first takes an existing project or directory and imports it into Git.
++The second clones an existing Git repository from another server.
+ 
+ ==== Initializing a Repository in an Existing Directory
+ 
+-If you have a project directory that is currently not under version control and you want to start controlling it with Git, you first need to go to that project's directory.
+-If you've never done this, it looks a little different depending on which system you're running:
++If you're starting to track an existing project in Git, you need to go to the project's directory and type:
+ 
+-for Linux:
+-[source,console]
+-----
+-$ cd /home/user/my_project
+-----
+-for macOS:
+-[source,console]
+-----
+-$ cd /Users/user/my_project
+-----
+-for Windows:
+-[source,console]
+-----
+-$ cd C:/Users/user/my_project
+-----
+-
+-and type:
+-
+-[source,console]
+-----
+-$ git init
+-----
+-
+-This creates a new subdirectory named `.git` that contains all of your necessary repository files -- a Git repository skeleton.
++This creates a new subdirectory named `.git` that contains all of your necessary repository files – a Git repository skeleton.
+ At this point, nothing in your project is tracked yet.
+-See <<ch10-git-internals#ch10-git-internals>> for more information about exactly what files are contained in the `.git` directory you just created.(((git commands, init)))
++(See <<ch10-git-internals#ch10-git-internals>> for more information about exactly what files are contained in the `.git` directory you just created.)(((git commands, init)))
+ 
+ If you want to start version-controlling existing files (as opposed to an empty directory), you should probably begin tracking those files and do an initial commit.
+ You can accomplish that with a few `git add` commands that specify the files you want to track, followed by a `git commit`:
+ 
+-[source,console]
+-----
+-$ git add *.c
+-$ git add LICENSE
+-$ git commit -m 'Initial project version'
+-----
+-
+ We'll go over what these commands do in just a minute.
+ At this point, you have a Git repository with tracked files and an initial commit.
+ 
+-[[_git_cloning]]
+ ==== Cloning an Existing Repository
+ 
+-If you want to get a copy of an existing Git repository -- for example, a project you'd like to contribute to -- the command you need is `git clone`.
++If you want to get a copy of an existing Git repository – for example, a project you'd like to contribute to – the command you need is `git clone`.
+ If you're familiar with other VCS systems such as Subversion, you'll notice that the command is "clone" and not "checkout".
+-This is an important distinction -- instead of getting just a working copy, Git receives a full copy of nearly all data that the server has.
++This is an important distinction – instead of getting just a working copy, Git receives a full copy of nearly all data that the server has.
+ Every version of every file for the history of the project is pulled down by default when you run `git clone`.
+-In fact, if your server disk gets corrupted, you can often use nearly any of the clones on any client to set the server back to the state it was in when it was cloned (you may lose some server-side hooks and such, but all the versioned data would be there -- see <<ch04-git-on-the-server#_getting_git_on_a_server>> for more details).
+-
+-You clone a repository with `git clone <url>`.(((git commands, clone)))
+-For example, if you want to clone the Git linkable library called `libgit2`, you can do so like this:
+-
+-[source,console]
+-----
+-$ git clone https://github.com/libgit2/libgit2
+-----
+-
+-That creates a directory named `libgit2`, initializes a `.git` directory inside it, pulls down all the data for that repository, and checks out a working copy of the latest version.
+-If you go into the new `libgit2` directory that was just created, you'll see the project files in there, ready to be worked on or used.
++In fact, if your server disk gets corrupted, you can often use nearly any of the clones on any client to set the server back to the state it was in when it was cloned (you may lose some server-side hooks and such, but all the versioned data would be there – see <<ch04-git-server#r_git_on_the_server>> for more details).
+ 
+-If you want to clone the repository into a directory named something other than `libgit2`, you can specify the new directory name as an additional argument:
++You clone a repository with `git clone [url]`.(((git commands, clone)))
++For example, if you want to clone the Git linkable library called libgit2, you can do so like this:
+ 
+-[source,console]
+-----
+-$ git clone https://github.com/libgit2/libgit2 mylibgit
+-----
++That creates a directory named ``libgit2'', initializes a `.git` directory inside it, pulls down all the data for that repository, and checks out a working copy of the latest version.
++If you go into the new `libgit2` directory, you'll see the project files in there, ready to be worked on or used.
++If you want to clone the repository into a directory named something other than ``libgit2'', you can specify that as the next command-line option:
+ 
+ That command does the same thing as the previous one, but the target directory is called `mylibgit`.
+ 
+ Git has a number of different transfer protocols you can use.
+ The previous example uses the `https://` protocol, but you may also see `git://` or `user@server:path/to/repo.git`, which uses the SSH transfer protocol.
+-<<ch04-git-on-the-server#_getting_git_on_a_server>> will introduce all of the available options the server can set up to access your Git repository and the pros and cons of each.
++<<ch04-git-server#r_git_on_the_server>> will introduce all of the available options the server can set up to access your Git repository and the pros and cons of each.
+diff -au ../../git/progit2/progit2/book/02-git-basics/sections/recording-changes.asc /tmp/book/02-git-basics/sections/recording-changes.asc.tmp
+--- ../../git/progit2/progit2/book/02-git-basics/sections/recording-changes.asc	2020-07-04 16:36:46.720685416 +0900
++++ /tmp/book/02-git-basics/sections/recording-changes.asc.tmp	2020-10-25 09:24:25.627965349 +0900
+@@ -1,91 +1,48 @@
+ === Recording Changes to the Repository
+ 
+-At this point, you should have a _bona fide_ Git repository on your local machine, and a checkout or _working copy_ of all of its files in front of you.
+-Typically, you'll want to start making changes and committing snapshots of those changes into your repository each time the project reaches a state you want to record.
++You have a bona fide Git repository and a checkout or working copy of the files for that project.
++You need to make some changes and commit snapshots of those changes into your repository each time the project reaches a state you want to record.
+ 
+-Remember that each file in your working directory can be in one of two states: _tracked_ or _untracked_.
++Remember that each file in your working directory can be in one of two states: tracked or untracked.
+ Tracked files are files that were in the last snapshot; they can be unmodified, modified, or staged.
+-In short, tracked files are files that Git knows about.
+-
+-Untracked files are everything else -- any files in your working directory that were not in your last snapshot and are not in your staging area.
+-When you first clone a repository, all of your files will be tracked and unmodified because Git just checked them out and you haven't edited anything.
++Untracked files are everything else – any files in your working directory that were not in your last snapshot and are not in your staging area.
++When you first clone a repository, all of your files will be tracked and unmodified because you just checked them out and haven't edited anything.
+ 
+ As you edit files, Git sees them as modified, because you've changed them since your last commit.
+-As you work, you selectively stage these modified files and then commit all those staged changes, and the cycle repeats.
++You stage these modified files and then commit all your staged changes, and the cycle repeats.
+ 
+-.The lifecycle of the status of your files
+-image::images/lifecycle.png[The lifecycle of the status of your files]
++.The lifecycle of the status of your files.
++image::images/lifecycle.png[The lifecycle of the status of your files.]
+ 
+-[[_checking_status]]
+ ==== Checking the Status of Your Files
+ 
+ The main tool you use to determine which files are in which state is the `git status` command.(((git commands, status)))
+ If you run this command directly after a clone, you should see something like this:
+ 
+-[source,console]
+-----
+-$ git status
+-On branch master
+-Your branch is up-to-date with 'origin/master'.
+-nothing to commit, working directory clean
+-----
+-
+-This means you have a clean working directory; in other words, none of your tracked files are modified.
++This means you have a clean working directory – in other words, there are no tracked and modified files.
+ Git also doesn't see any untracked files, or they would be listed here.
+ Finally, the command tells you which branch you're on and informs you that it has not diverged from the same branch on the server.
+-For now, that branch is always `master`, which is the default; you won't worry about it here.
+-<<ch03-git-branching#ch03-git-branching>> will go over branches and references in detail.
++For now, that branch is always ``master'', which is the default; you won't worry about it here.
++<<ch03-git-branching#ch03-git-branching>>  will go over branches and references in detail.
+ 
+-Let's say you add a new file to your project, a simple `README` file.
++Let's say you add a new file to your project, a simple README file.
+ If the file didn't exist before, and you run `git status`, you see your untracked file like so:
+ 
+-[source,console]
+-----
+-$ echo 'My Project' > README
+-$ git status
+-On branch master
+-Your branch is up-to-date with 'origin/master'.
+-Untracked files:
+-  (use "git add <file>..." to include in what will be committed)
+-
+-    README
+-
+-nothing added to commit but untracked files present (use "git add" to track)
+-----
+-
+-You can see that your new `README` file is untracked, because it's under the ``Untracked files'' heading in your status output.
++You can see that your new README file is untracked, because it's under the ``Untracked files'' heading in your status output.
+ Untracked basically means that Git sees a file you didn't have in the previous snapshot (commit); Git won't start including it in your commit snapshots until you explicitly tell it to do so.
+ It does this so you don't accidentally begin including generated binary files or other files that you did not mean to include.
+-You do want to start including `README`, so let's start tracking the file.
++You do want to start including README, so let's start tracking the file.
+ 
+-[[_tracking_files]]
+ ==== Tracking New Files
+ 
+ In order to begin tracking a new file, you use the command `git add`.(((git commands, add)))
+-To begin tracking the `README` file, you can run this:
+-
+-[source,console]
+-----
+-$ git add README
+-----
+-
+-If you run your status command again, you can see that your `README` file is now tracked and staged to be committed:
+-
+-[source,console]
+-----
+-$ git status
+-On branch master
+-Your branch is up-to-date with 'origin/master'.
+-Changes to be committed:
+-  (use "git restore --staged <file>..." to unstage)
++To begin tracking the README file, you can run this:
+ 
+-    new file:   README
+-
+-----
++If you run your status command again, you can see that your README file is now tracked and staged to be committed:
+ 
+ You can tell that it's staged because it's under the ``Changes to be committed'' heading.
+-If you commit at this point, the version of the file at the time you ran `git add` is what will be in the subsequent historical snapshot.
+-You may recall that when you ran `git init` earlier, you then ran `git add <files>` -- that was to begin tracking files in your directory.(((git commands, init)))(((git commands, add)))
++If you commit at this point, the version of the file at the time you ran `git add` is what will be in the historical snapshot.
++You may recall that when you ran `git init` earlier, you then ran `git add (files)` – that was to begin tracking files in your directory.(((git commands, init)))(((git commands, add)))
+ The `git add` command takes a path name for either a file or a directory; if it's a directory, the command adds all the files in that directory recursively.
+ 
+ ==== Staging Modified Files
+@@ -93,69 +50,17 @@
+ Let's change a file that was already tracked.
+ If you change a previously tracked file called `CONTRIBUTING.md` and then run your `git status` command again, you get something that looks like this:
+ 
+-[source,console]
+-----
+-$ git status
+-On branch master
+-Your branch is up-to-date with 'origin/master'.
+-Changes to be committed:
+-  (use "git reset HEAD <file>..." to unstage)
+-
+-    new file:   README
+-
+-Changes not staged for commit:
+-  (use "git add <file>..." to update what will be committed)
+-  (use "git checkout -- <file>..." to discard changes in working directory)
+-
+-    modified:   CONTRIBUTING.md
+-
+-----
+-
+-The `CONTRIBUTING.md` file appears under a section named ``Changes not staged for commit'' -- which means that a file that is tracked has been modified in the working directory but not yet staged.
++The `CONTRIBUTING.md` file appears under a section named ``Changes not staged for commit'' – which means that a file that is tracked has been modified in the working directory but not yet staged.
+ To stage it, you run the `git add` command.
+-`git add` is a multipurpose command -- you use it to begin tracking new files, to stage files, and to do other things like marking merge-conflicted files as resolved.
+-It may be helpful to think of it more as ``add precisely this content to the next commit'' rather than ``add this file to the project''.(((git commands, add)))
++`git add` is a multipurpose command – you use it to begin tracking new files, to stage files, and to do other things like marking merge-conflicted files as resolved.
++It may be helpful to think of it more as ``add this content to the next commit'' rather than ``add this file to the project''.(((git commands, add)))
+ Let's run `git add` now to stage the `CONTRIBUTING.md` file, and then run `git status` again:
+ 
+-[source,console]
+-----
+-$ git add CONTRIBUTING.md
+-$ git status
+-On branch master
+-Your branch is up-to-date with 'origin/master'.
+-Changes to be committed:
+-  (use "git reset HEAD <file>..." to unstage)
+-
+-    new file:   README
+-    modified:   CONTRIBUTING.md
+-
+-----
+-
+ Both files are staged and will go into your next commit.
+ At this point, suppose you remember one little change that you want to make in `CONTRIBUTING.md` before you commit it.
+ You open it again and make that change, and you're ready to commit.
+ However, let's run `git status` one more time:
+ 
+-[source,console]
+-----
+-$ vim CONTRIBUTING.md
+-$ git status
+-On branch master
+-Your branch is up-to-date with 'origin/master'.
+-Changes to be committed:
+-  (use "git reset HEAD <file>..." to unstage)
+-
+-    new file:   README
+-    modified:   CONTRIBUTING.md
+-
+-Changes not staged for commit:
+-  (use "git add <file>..." to update what will be committed)
+-  (use "git checkout -- <file>..." to discard changes in working directory)
+-
+-    modified:   CONTRIBUTING.md
+-
+-----
+-
+ What the heck?
+ Now `CONTRIBUTING.md` is listed as both staged _and_ unstaged.
+ How is that possible?
+@@ -163,41 +68,17 @@
+ If you commit now, the version of `CONTRIBUTING.md` as it was when you last ran the `git add` command is how it will go into the commit, not the version of the file as it looks in your working directory when you run `git commit`.
+ If you modify a file after you run `git add`, you have to run `git add` again to stage the latest version of the file:
+ 
+-[source,console]
+-----
+-$ git add CONTRIBUTING.md
+-$ git status
+-On branch master
+-Your branch is up-to-date with 'origin/master'.
+-Changes to be committed:
+-  (use "git reset HEAD <file>..." to unstage)
+-
+-    new file:   README
+-    modified:   CONTRIBUTING.md
+-----
+-
+ ==== Short Status
+ 
+ While the `git status` output is pretty comprehensive, it's also quite wordy.
+ Git also has a short status flag so you can see your changes in a more compact way.
+ If you run `git status -s` or `git status --short` you get a far more simplified output from the command:
+ 
+-[source,console]
+-----
+-$ git status -s
+- M README
+-MM Rakefile
+-A  lib/git.rb
+-M  lib/simplegit.rb
+-?? LICENSE.txt
+-----
+-
+ New files that aren't tracked have a `??` next to them, new files that have been added to the staging area have an `A`, modified files have an `M` and so on.
+-There are two columns to the output -- the left-hand column indicates the status of the staging area and the right-hand column indicates the status of the working tree.
++There are two columns to the output - the left hand column indicates that the file is staged and the right hand column indicates that it's modified.
+ So for example in that output, the `README` file is modified in the working directory but not yet staged, while the `lib/simplegit.rb` file is modified and staged.
+ The `Rakefile` was modified, staged and then modified again, so there are changes to it that are both staged and unstaged.
+ 
+-[[_ignoring]]
+ ==== Ignoring Files
+ 
+ Often, you'll have a class of files that you don't want Git to automatically add or even show you as being untracked.
+@@ -205,198 +86,57 @@
+ In such cases, you can create a file listing patterns to match them named `.gitignore`.(((ignoring files)))
+ Here is an example `.gitignore` file:
+ 
+-[source,console]
+-----
+-$ cat .gitignore
+-*.[oa]
+-*~
+-----
+-
+-The first line tells Git to ignore any files ending in ``.o'' or ``.a'' -- object and archive files that may be the product of building your code.
+-The second line tells Git to ignore all files whose names end with a tilde (`~`), which is used by many text editors such as Emacs to mark temporary files.
++The first line tells Git to ignore any files ending in ``.o'' or ``.a'' – object and archive files that may be the product of building your code.
++The second line tells Git to ignore all files that end with a tilde (`~`), which is used by many text editors such as Emacs to mark temporary files.
+ You may also include a log, tmp, or pid directory; automatically generated documentation; and so on.
+-Setting up a `.gitignore` file for your new repository before you get going is generally a good idea so you don't accidentally commit files that you really don't want in your Git repository.
++Setting up a `.gitignore` file before you get going is generally a good idea so you don't accidentally commit files that you really don't want in your Git repository.
+ 
+ The rules for the patterns you can put in the `.gitignore` file are as follows:
+ 
+ *  Blank lines or lines starting with `#` are ignored.
+-*  Standard glob patterns work, and will be applied recursively throughout the entire working tree.
++*  Standard glob patterns work.
+ *  You can start patterns with a forward slash (`/`) to avoid recursivity.
+ *  You can end patterns with a forward slash (`/`) to specify a directory.
+ *  You can negate a pattern by starting it with an exclamation point (`!`).
+ 
+ Glob patterns are like simplified regular expressions that shells use.
+-An asterisk (`*`) matches zero or more characters; `[abc]` matches any character inside the brackets (in this case a, b, or c); a question mark (`?`) matches a single character; and brackets enclosing characters separated by a hyphen (`[0-9]`) matches any character between them (in this case 0 through 9).
++An asterisk (`*`) matches zero or more characters; `[abc]` matches any character inside the brackets (in this case a, b, or c); a question mark (`?`) matches a single character; and brackets enclosing characters separated by a hyphen(`[0-9]`) matches any character between them (in this case 0 through 9).
+ You can also use two asterisks to match nested directories; `a/**/z` would match `a/z`, `a/b/z`, `a/b/c/z`, and so on.
+ 
+-Here is another example `.gitignore` file:
+-
+-[source]
+-----
+-# ignore all .a files
+-*.a
+-
+-# but do track lib.a, even though you're ignoring .a files above
+-!lib.a
+-
+-# only ignore the TODO file in the current directory, not subdir/TODO
+-/TODO
++Here is another example .gitignore file:
+ 
+-# ignore all files in any directory named build
+-build/
+-
+-# ignore doc/notes.txt, but not doc/server/arch.txt
+-doc/*.txt
+-
+-# ignore all .pdf files in the doc/ directory and any of its subdirectories
+-doc/**/*.pdf
+-----
+-
+-[TIP]
+ ====
+ GitHub maintains a fairly comprehensive list of good `.gitignore` file examples for dozens of projects and languages at https://github.com/github/gitignore[] if you want a starting point for your project.
+ ====
+ 
+-[NOTE]
+-====
+-In the simple case, a repository might have a single `.gitignore` file in its root directory, which applies recursively to the entire repository.
+-However, it is also possible to have additional `.gitignore` files in subdirectories.
+-The rules in these nested `.gitignore` files apply only to the files under the directory where they are located.
+-The Linux kernel source repository has 206 `.gitignore` files.
+-
+-It is beyond the scope of this book to get into the details of multiple `.gitignore` files; see `man gitignore` for the details.
+-====
+-
+-[[_git_diff_staged]]
+ ==== Viewing Your Staged and Unstaged Changes
+ 
+-If the `git status` command is too vague for you -- you want to know exactly what you changed, not just which files were changed -- you can use the `git diff` command.(((git commands, diff)))
++If the `git status` command is too vague for you – you want to know exactly what you changed, not just which files were changed – you can use the `git diff` command.(((git commands, diff)))
+ We'll cover `git diff` in more detail later, but you'll probably use it most often to answer these two questions: What have you changed but not yet staged?
+ And what have you staged that you are about to commit?
+-Although `git status` answers those questions very generally by listing the file names, `git diff` shows you the exact lines added and removed -- the patch, as it were.
++Although `git status` answers those questions very generally by listing the file names, `git diff` shows you the exact lines added and removed – the patch, as it were.
+ 
+ Let's say you edit and stage the `README` file again and then edit the `CONTRIBUTING.md` file without staging it.
+ If you run your `git status` command, you once again see something like this:
+ 
+-[source,console]
+-----
+-$ git status
+-On branch master
+-Your branch is up-to-date with 'origin/master'.
+-Changes to be committed:
+-  (use "git reset HEAD <file>..." to unstage)
+-
+-    modified:   README
+-
+-Changes not staged for commit:
+-  (use "git add <file>..." to update what will be committed)
+-  (use "git checkout -- <file>..." to discard changes in working directory)
+-
+-    modified:   CONTRIBUTING.md
+-----
+-
+ To see what you've changed but not yet staged, type `git diff` with no other arguments:
+ 
+-[source,console]
+-----
+-$ git diff
+-diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
+-index 8ebb991..643e24f 100644
+---- a/CONTRIBUTING.md
+-+++ b/CONTRIBUTING.md
+-@@ -65,7 +65,8 @@ branch directly, things can get messy.
+- Please include a nice description of your changes when you submit your PR;
+- if we have to read the whole diff to figure out why you're contributing
+- in the first place, you're less likely to get feedback and have your change
+--merged in.
+-+merged in. Also, split your changes into comprehensive chunks if your patch is
+-+longer than a dozen lines.
+-
+- If you are starting to work on a particular area, feel free to submit a PR
+- that highlights your work in progress (and note in the PR title that it's
+-----
+-
+ That command compares what is in your working directory with what is in your staging area.
+ The result tells you the changes you've made that you haven't yet staged.
+ 
+ If you want to see what you've staged that will go into your next commit, you can use `git diff --staged`.
+ This command compares your staged changes to your last commit:
+ 
+-[source,console]
+-----
+-$ git diff --staged
+-diff --git a/README b/README
+-new file mode 100644
+-index 0000000..03902a1
+---- /dev/null
+-+++ b/README
+-@@ -0,0 +1 @@
+-+My Project
+-----
+-
+-It's important to note that `git diff` by itself doesn't show all changes made since your last commit -- only changes that are still unstaged.
+-If you've staged all of your changes, `git diff` will give you no output.
++It's important to note that `git diff` by itself doesn't show all changes made since your last commit – only changes that are still unstaged.
++This can be confusing, because if you've staged all of your changes, `git diff` will give you no output.
+ 
+ For another example, if you stage the `CONTRIBUTING.md` file and then edit it, you can use `git diff` to see the changes in the file that are staged and the changes that are unstaged.
+ If our environment looks like this:
+ 
+-[source,console]
+-----
+-$ git add CONTRIBUTING.md
+-$ echo '# test line' >> CONTRIBUTING.md
+-$ git status
+-On branch master
+-Your branch is up-to-date with 'origin/master'.
+-Changes to be committed:
+-  (use "git reset HEAD <file>..." to unstage)
+-
+-    modified:   CONTRIBUTING.md
+-
+-Changes not staged for commit:
+-  (use "git add <file>..." to update what will be committed)
+-  (use "git checkout -- <file>..." to discard changes in working directory)
+-
+-    modified:   CONTRIBUTING.md
+-----
+-
+ Now you can use `git diff` to see what is still unstaged:
+ 
+-[source,console]
+-----
+-$ git diff
+-diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
+-index 643e24f..87f08c8 100644
+---- a/CONTRIBUTING.md
+-+++ b/CONTRIBUTING.md
+-@@ -119,3 +119,4 @@ at the
+- ## Starter Projects
+-
+- See our [projects list](https://github.com/libgit2/libgit2/blob/development/PROJECTS.md).
+-+# test line
+-----
+-
+ and `git diff --cached` to see what you've staged so far (`--staged` and `--cached` are synonyms):
+ 
+-[source,console]
+-----
+-$ git diff --cached
+-diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
+-index 8ebb991..643e24f 100644
+---- a/CONTRIBUTING.md
+-+++ b/CONTRIBUTING.md
+-@@ -65,7 +65,8 @@ branch directly, things can get messy.
+- Please include a nice description of your changes when you submit your PR;
+- if we have to read the whole diff to figure out why you're contributing
+- in the first place, you're less likely to get feedback and have your change
+--merged in.
+-+merged in. Also, split your changes into comprehensive chunks if your patch is
+-+longer than a dozen lines.
+-
+- If you are starting to work on a particular area, feel free to submit a PR
+- that highlights your work in progress (and note in the PR title that it's
+-----
+-
+-[NOTE]
+ .Git Diff in an External Tool
+ ====
+ We will continue to use the `git diff` command in various ways throughout the rest of the book.
+@@ -405,68 +145,27 @@
+ Run `git difftool --tool-help` to see what is available on your system.
+ ====
+ 
+-[[_committing_changes]]
+ ==== Committing Your Changes
+ 
+ Now that your staging area is set up the way you want it, you can commit your changes.
+-Remember that anything that is still unstaged -- any files you have created or modified that you haven't run `git add` on since you edited them -- won't go into this commit.
++Remember that anything that is still unstaged – any files you have created or modified that you haven't run `git add` on since you edited them – won't go into this commit.
+ They will stay as modified files on your disk.
+ In this case, let's say that the last time you ran `git status`, you saw that everything was staged, so you're ready to commit your changes.(((git commands, status)))
+ The simplest way to commit is to type `git commit`:(((git commands, commit)))
+ 
+-[source,console]
+-----
+-$ git commit
+-----
+-
+ Doing so launches your editor of choice.
+-
+-[NOTE]
+-====
+-This is set by your shell's `EDITOR` environment variable -- usually vim or emacs, although you can configure it with whatever you want using the `git config --global core.editor` command as you saw in <<ch01-getting-started#ch01-getting-started>>.(((editor, changing default)))(((git commands, config)))
+-====
++(This is set by your shell's `$EDITOR` environment variable – usually vim or emacs, although you can configure it with whatever you want using the `git config --global core.editor` command as you saw in <<ch01-introduction#ch01-introduction>>).(((editor, changing default)))(((git commands, config)))
+ 
+ The editor displays the following text (this example is a Vim screen):
+ 
+-[source]
+-----
+-
+-# Please enter the commit message for your changes. Lines starting
+-# with '#' will be ignored, and an empty message aborts the commit.
+-# On branch master
+-# Your branch is up-to-date with 'origin/master'.
+-#
+-# Changes to be committed:
+-#	new file:   README
+-#	modified:   CONTRIBUTING.md
+-#
+-~
+-~
+-~
+-".git/COMMIT_EDITMSG" 9L, 283C
+-----
+-
+ You can see that the default commit message contains the latest output of the `git status` command commented out and one empty line on top.
+ You can remove these comments and type your commit message, or you can leave them there to help you remember what you're committing.
+-
+-[NOTE]
+-====
+-For an even more explicit reminder of what you've modified, you can pass the `-v` option to `git commit`.
+-Doing so also puts the diff of your change in the editor so you can see exactly what changes you're committing.
+-====
+-
++(For an even more explicit reminder of what you've modified, you can pass the `-v` option to `git commit`.
++Doing so also puts the diff of your change in the editor so you can see exactly what changes you're committing.)
+ When you exit the editor, Git creates your commit with that commit message (with the comments and diff stripped out).
+ 
+ Alternatively, you can type your commit message inline with the `commit` command by specifying it after a `-m` flag, like this:
+ 
+-[source,console]
+-----
+-$ git commit -m "Story 182: fix benchmarks for speed"
+-[master 463dc4f] Story 182: fix benchmarks for speed
+- 2 files changed, 2 insertions(+)
+- create mode 100644 README
+-----
+-
+ Now you've created your first commit!
+ You can see that the commit has given you some output about itself: which branch you committed to (`master`), what SHA-1 checksum the commit has (`463dc4f`), how many files were changed, and statistics about lines added and removed in the commit.
+ 
+@@ -476,73 +175,25 @@
+ 
+ ==== Skipping the Staging Area
+ 
+-(((staging area, skipping)))
+ Although it can be amazingly useful for crafting commits exactly how you want them, the staging area is sometimes a bit more complex than you need in your workflow.
+ If you want to skip the staging area, Git provides a simple shortcut.
+ Adding the `-a` option to the `git commit` command makes Git automatically stage every file that is already tracked before doing the commit, letting you skip the `git add` part:
+ 
+-[source,console]
+-----
+-$ git status
+-On branch master
+-Your branch is up-to-date with 'origin/master'.
+-Changes not staged for commit:
+-  (use "git add <file>..." to update what will be committed)
+-  (use "git checkout -- <file>..." to discard changes in working directory)
+-
+-    modified:   CONTRIBUTING.md
+-
+-no changes added to commit (use "git add" and/or "git commit -a")
+-$ git commit -a -m 'Add new benchmarks'
+-[master 83e38c7] Add new benchmarks
+- 1 file changed, 5 insertions(+), 0 deletions(-)
+-----
+-
+ Notice how you don't have to run `git add` on the `CONTRIBUTING.md` file in this case before you commit.
+ That's because the `-a` flag includes all changed files.
+ This is convenient, but be careful; sometimes this flag will cause you to include unwanted changes.
+ 
+-[[_removing_files]]
+ ==== Removing Files
+ 
+-(((files, removing)))
+ To remove a file from Git, you have to remove it from your tracked files (more accurately, remove it from your staging area) and then commit.
+ The `git rm` command does that, and also removes the file from your working directory so you don't see it as an untracked file the next time around.
+ 
+-If you simply remove the file from your working directory, it shows up under the ``Changes not staged for commit'' (that is, _unstaged_) area of your `git status` output:
+-
+-[source,console]
+-----
+-$ rm PROJECTS.md
+-$ git status
+-On branch master
+-Your branch is up-to-date with 'origin/master'.
+-Changes not staged for commit:
+-  (use "git add/rm <file>..." to update what will be committed)
+-  (use "git checkout -- <file>..." to discard changes in working directory)
+-
+-        deleted:    PROJECTS.md
+-
+-no changes added to commit (use "git add" and/or "git commit -a")
+-----
++If you simply remove the file from your working directory, it shows up under the ``Changed but not updated'' (that is, _unstaged_) area of your `git status` output:
+ 
+ Then, if you run `git rm`, it stages the file's removal:
+ 
+-[source,console]
+-----
+-$ git rm PROJECTS.md
+-rm 'PROJECTS.md'
+-$ git status
+-On branch master
+-Your branch is up-to-date with 'origin/master'.
+-Changes to be committed:
+-  (use "git reset HEAD <file>..." to unstage)
+-
+-    deleted:    PROJECTS.md
+-----
+-
+ The next time you commit, the file will be gone and no longer tracked.
+-If you modified the file or had already added it to the staging area, you must force the removal with the `-f` option.
++If you modified the file and added it to the index already, you must force the removal with the `-f` option.
+ This is a safety feature to prevent accidental removal of data that hasn't yet been recorded in a snapshot and that can't be recovered from Git.
+ 
+ Another useful thing you may want to do is to keep the file in your working tree but remove it from your staging area.
+@@ -550,71 +201,30 @@
+ This is particularly useful if you forgot to add something to your `.gitignore` file and accidentally staged it, like a large log file or a bunch of `.a` compiled files.
+ To do this, use the `--cached` option:
+ 
+-[source,console]
+-----
+-$ git rm --cached README
+-----
+-
+ You can pass files, directories, and file-glob patterns to the `git rm` command.
+ That means you can do things such as:
+ 
+-[source,console]
+-----
+-$ git rm log/\*.log
+-----
+-
+ Note the backslash (`\`) in front of the `*`.
+ This is necessary because Git does its own filename expansion in addition to your shell's filename expansion.
+ This command removes all files that have the `.log` extension in the `log/` directory.
+ Or, you can do something like this:
+ 
+-[source,console]
+-----
+-$ git rm \*~
+-----
++This command removes all files that end with `~`.
+ 
+-This command removes all files whose names end with a `~`.
+-
+-[[_git_mv]]
+ ==== Moving Files
+ 
+-(((files, moving)))
+ Unlike many other VCS systems, Git doesn't explicitly track file movement.
+ If you rename a file in Git, no metadata is stored in Git that tells it you renamed the file.
+-However, Git is pretty smart about figuring that out after the fact -- we'll deal with detecting file movement a bit later.
++However, Git is pretty smart about figuring that out after the fact – we'll deal with detecting file movement a bit later.
+ 
+ Thus it's a bit confusing that Git has a `mv` command.
+ If you want to rename a file in Git, you can run something like:
+ 
+-[source,console]
+-----
+-$ git mv file_from file_to
+-----
+-
+ and it works fine.
+ In fact, if you run something like this and look at the status, you'll see that Git considers it a renamed file:
+ 
+-[source,console]
+-----
+-$ git mv README.md README
+-$ git status
+-On branch master
+-Your branch is up-to-date with 'origin/master'.
+-Changes to be committed:
+-  (use "git reset HEAD <file>..." to unstage)
+-
+-    renamed:    README.md -> README
+-----
+-
+ However, this is equivalent to running something like this:
+ 
+-[source,console]
+-----
+-$ mv README.md README
+-$ git rm README.md
+-$ git add README
+-----
+-
+ Git figures out that it's a rename implicitly, so it doesn't matter if you rename a file that way or with the `mv` command.
+-The only real difference is that `git mv` is one command instead of three -- it's a convenience function.
++The only real difference is that `mv` is one command instead of three – it's a convenience function.
+ More importantly, you can use any tool you like to rename a file, and address the add/rm later, before you commit.
+diff -au ../../git/progit2/progit2/book/02-git-basics/sections/remotes.asc /tmp/book/02-git-basics/sections/remotes.asc.tmp
+--- ../../git/progit2/progit2/book/02-git-basics/sections/remotes.asc	2020-07-17 09:06:42.261936072 +0900
++++ /tmp/book/02-git-basics/sections/remotes.asc.tmp	2020-10-25 09:24:25.633965632 +0900
+@@ -1,4 +1,4 @@
+-[[_remote_repos]]
++[[r_remote_repos]]
+ === Working with Remotes
+ 
+ To be able to collaborate on any Git project, you need to know how to manage your remote repositories.
+@@ -8,233 +8,81 @@
+ Managing remote repositories includes knowing how to add remote repositories, remove remotes that are no longer valid, manage various remote branches and define them as being tracked or not, and more.
+ In this section, we'll cover some of these remote-management skills.
+ 
+-[NOTE]
+-.Remote repositories can be on your local machine.
+-====
+-It is entirely possible that you can be working with a ``remote'' repository that is, in fact, on the same host you are.
+-The word ``remote'' does not necessarily imply that the repository is somewhere else on the network or Internet, only that it is elsewhere.
+-Working with such a remote repository would still involve all the standard pushing, pulling and fetching operations as with any other remote.
+-====
+-
+ ==== Showing Your Remotes
+ 
+ To see which remote servers you have configured, you can run the `git remote` command.(((git commands, remote)))
+ It lists the shortnames of each remote handle you've specified.
+-If you've cloned your repository, you should at least see `origin` -- that is the default name Git gives to the server you cloned from:
+-
+-[source,console]
+-----
+-$ git clone https://github.com/schacon/ticgit
+-Cloning into 'ticgit'...
+-remote: Reusing existing pack: 1857, done.
+-remote: Total 1857 (delta 0), reused 0 (delta 0)
+-Receiving objects: 100% (1857/1857), 374.35 KiB | 268.00 KiB/s, done.
+-Resolving deltas: 100% (772/772), done.
+-Checking connectivity... done.
+-$ cd ticgit
+-$ git remote
+-origin
+-----
++If you've cloned your repository, you should at least see origin – that is the default name Git gives to the server you cloned from:
+ 
+ You can also specify `-v`, which shows you the URLs that Git has stored for the shortname to be used when reading and writing to that remote:
+ 
+-[source,console]
+-----
+-$ git remote -v
+-origin	https://github.com/schacon/ticgit (fetch)
+-origin	https://github.com/schacon/ticgit (push)
+-----
+-
+ If you have more than one remote, the command lists them all.
+ For example, a repository with multiple remotes for working with several collaborators might look something like this.
+ 
+-[source,console]
+-----
+-$ cd grit
+-$ git remote -v
+-bakkdoor  https://github.com/bakkdoor/grit (fetch)
+-bakkdoor  https://github.com/bakkdoor/grit (push)
+-cho45     https://github.com/cho45/grit (fetch)
+-cho45     https://github.com/cho45/grit (push)
+-defunkt   https://github.com/defunkt/grit (fetch)
+-defunkt   https://github.com/defunkt/grit (push)
+-koke      git://github.com/koke/grit.git (fetch)
+-koke      git://github.com/koke/grit.git (push)
+-origin    [e-mail]:mojombo/grit.git (fetch)
+-origin    [e-mail]:mojombo/grit.git (push)
+-----
+-
+ This means we can pull contributions from any of these users pretty easily.
+ We may additionally have permission to push to one or more of these, though we can't tell that here.
+ 
+-Notice that these remotes use a variety of protocols; we'll cover more about this in <<ch04-git-on-the-server#_getting_git_on_a_server>>.
++Notice that these remotes use a variety of protocols; we'll cover more about this in <<ch04-git-server#r_git_on_the_server>>.
+ 
+ ==== Adding Remote Repositories
+ 
+-We've mentioned and given some demonstrations of how the `git clone` command implicitly adds the `origin` remote for you.
+-Here's how to add a new remote explicitly.(((git commands, remote)))
++We've mentioned and given some demonstrations of adding remote repositories in previous sections, but here is how to do it explicitly.(((git commands, remote)))
+ To add a new remote Git repository as a shortname you can reference easily, run `git remote add <shortname> <url>`:
+ 
+-[source,console]
+-----
+-$ git remote
+-origin
+-$ git remote add pb https://github.com/paulboone/ticgit
+-$ git remote -v
+-origin	https://github.com/schacon/ticgit (fetch)
+-origin	https://github.com/schacon/ticgit (push)
+-pb	https://github.com/paulboone/ticgit (fetch)
+-pb	https://github.com/paulboone/ticgit (push)
+-----
+-
+ Now you can use the string `pb` on the command line in lieu of the whole URL.
+ For example, if you want to fetch all the information that Paul has but that you don't yet have in your repository, you can run `git fetch pb`:
+ 
+-[source,console]
+-----
+-$ git fetch pb
+-remote: Counting objects: 43, done.
+-remote: Compressing objects: 100% (36/36), done.
+-remote: Total 43 (delta 10), reused 31 (delta 5)
+-Unpacking objects: 100% (43/43), done.
+-From https://github.com/paulboone/ticgit
+- * [new branch]      master     -> pb/master
+- * [new branch]      ticgit     -> pb/ticgit
+-----
+-
+-Paul's `master` branch is now accessible locally as `pb/master` -- you can merge it into one of your branches, or you can check out a local branch at that point if you want to inspect it.
+-We'll go over what branches are and how to use them in much more detail in <<ch03-git-branching#ch03-git-branching>>.
++Paul's master branch is now accessible locally as `pb/master` – you can merge it into one of your branches, or you can check out a local branch at that point if you want to inspect it.
++(We'll go over what branches are and how to use them in much more detail in <<ch03-git-branching#ch03-git-branching>>.)
+ 
+-[[_fetching_and_pulling]]
+ ==== Fetching and Pulling from Your Remotes
+ 
+ As you just saw, to get data from your remote projects, you can run:(((git commands, fetch)))
+ 
+-[source,console]
+-----
+-$ git fetch <remote>
+-----
+-
+ The command goes out to that remote project and pulls down all the data from that remote project that you don't have yet.
+ After you do this, you should have references to all the branches from that remote, which you can merge in or inspect at any time.
+ 
+ If you clone a repository, the command automatically adds that remote repository under the name ``origin''.
+ So, `git fetch origin` fetches any new work that has been pushed to that server since you cloned (or last fetched from) it.
+-It's important to note that the `git fetch` command only downloads the data to your local repository -- it doesn't automatically merge it with any of your work or modify what you're currently working on.
++It's important to note that the `git fetch` command pulls the data to your local repository – it doesn't automatically merge it with any of your work or modify what you're currently working on.
+ You have to merge it manually into your work when you're ready.
+ 
+-If your current branch is set up to track a remote branch (see the next section and <<ch03-git-branching#ch03-git-branching>> for more information), you can use the `git pull` command to automatically fetch and then merge that remote branch into your current branch.(((git commands, pull)))
+-This may be an easier or more comfortable workflow for you; and by default, the `git clone` command automatically sets up your local `master` branch to track the remote `master` branch (or whatever the default branch is called) on the server you cloned from.
++If you have a branch set up to track a remote branch (see the next section and <<ch03-git-branching#ch03-git-branching>> for more information), you can use the `git pull` command to automatically fetch and then merge a remote branch into your current branch.(((git commands, pull)))
++This may be an easier or more comfortable workflow for you; and by default, the `git clone` command automatically sets up your local master branch to track the remote master branch (or whatever the default branch is called) on the server you cloned from.
+ Running `git pull` generally fetches data from the server you originally cloned from and automatically tries to merge it into the code you're currently working on.
+ 
+-[NOTE]
+-====
+-From git version 2.27 onward, `git pull` will give a warning if the `pull.rebase` variable is not set.
+-Git will keep warning you until you set the variable.
+-
+-If you want the default behavior of git (fast-forward if possible, else create a merge commit):
+-`git config --global pull.rebase "false"`
+-
+-If you want to rebase when pulling:
+-`git config --global pull.rebase "true"`
+-====
+-
+-[[_pushing_remotes]]
+ ==== Pushing to Your Remotes
+ 
+ When you have your project at a point that you want to share, you have to push it upstream.
+-The command for this is simple: `git push <remote> <branch>`.(((git commands, push)))
+-If you want to push your `master` branch to your `origin` server (again, cloning generally sets up both of those names for you automatically), then you can run this to push any commits you've done back up to the server:
+-
+-[source,console]
+-----
+-$ git push origin master
+-----
++The command for this is simple: `git push [remote-name] [branch-name]`.(((git commands, push)))
++If you want to push your master branch to your `origin` server (again, cloning generally sets up both of those names for you automatically), then you can run this to push any commits you've done back up to the server:
+ 
+ This command works only if you cloned from a server to which you have write access and if nobody has pushed in the meantime.
+ If you and someone else clone at the same time and they push upstream and then you push upstream, your push will rightly be rejected.
+-You'll have to fetch their work first and incorporate it into yours before you'll be allowed to push.
++You'll have to pull down their work first and incorporate it into yours before you'll be allowed to push.
+ See <<ch03-git-branching#ch03-git-branching>> for more detailed information on how to push to remote servers.
+ 
+-[[_inspecting_remote]]
+ ==== Inspecting a Remote
+ 
+-If you want to see more information about a particular remote, you can use the `git remote show <remote>` command.(((git commands, remote)))
++If you want to see more information about a particular remote, you can use the `git remote show [remote-name]` command.(((git commands, remote)))
+ If you run this command with a particular shortname, such as `origin`, you get something like this:
+ 
+-[source,console]
+-----
+-$ git remote show origin
+-* remote origin
+-  Fetch URL: https://github.com/schacon/ticgit
+-  Push  URL: https://github.com/schacon/ticgit
+-  HEAD branch: master
+-  Remote branches:
+-    master                               tracked
+-    dev-branch                           tracked
+-  Local branch configured for 'git pull':
+-    master merges with remote master
+-  Local ref configured for 'git push':
+-    master pushes to master (up to date)
+-----
+-
+ It lists the URL for the remote repository as well as the tracking branch information.
+-The command helpfully tells you that if you're on the `master` branch and you run `git pull`, it will automatically merge in the `master` branch on the remote after it fetches all the remote references.
++The command helpfully tells you that if you're on the master branch and you run `git pull`, it will automatically merge in the master branch on the remote after it fetches all the remote references.
+ It also lists all the remote references it has pulled down.
+ 
+ That is a simple example you're likely to encounter.
+ When you're using Git more heavily, however, you may see much more information from `git remote show`:
+ 
+-[source,console]
+-----
+-$ git remote show origin
+-* remote origin
+-  URL: https://github.com/my-org/complex-project
+-  Fetch URL: https://github.com/my-org/complex-project
+-  Push  URL: https://github.com/my-org/complex-project
+-  HEAD branch: master
+-  Remote branches:
+-    master                           tracked
+-    dev-branch                       tracked
+-    markdown-strip                   tracked
+-    issue-43                         new (next fetch will store in remotes/origin)
+-    issue-45                         new (next fetch will store in remotes/origin)
+-    refs/remotes/origin/issue-11     stale (use 'git remote prune' to remove)
+-  Local branches configured for 'git pull':
+-    dev-branch merges with remote dev-branch
+-    master     merges with remote master
+-  Local refs configured for 'git push':
+-    dev-branch                     pushes to dev-branch                     (up to date)
+-    markdown-strip                 pushes to markdown-strip                 (up to date)
+-    master                         pushes to master                         (up to date)
+-----
+-
+ This command shows which branch is automatically pushed to when you run `git push` while on certain branches.
+-It also shows you which remote branches on the server you don't yet have, which remote branches you have that have been removed from the server, and multiple local branches that are able to merge automatically with their remote-tracking branch when you run `git pull`.
++It also shows you which remote branches on the server you don't yet have, which remote branches you have that have been removed from the server, and multiple branches that are automatically merged when you run `git pull`.
+ 
+-==== Renaming and Removing Remotes
++==== Removing and Renaming Remotes
+ 
+-You can run `git remote rename` to change a remote's shortname.(((git commands, remote)))
++If you want to rename a reference you can run `git remote rename` to change a remote's shortname.(((git commands, remote)))
+ For instance, if you want to rename `pb` to `paul`, you can do so with `git remote rename`:
+ 
+-[source,console]
+-----
+-$ git remote rename pb paul
+-$ git remote
+-origin
+-paul
+-----
+-
+-It's worth mentioning that this changes all your remote-tracking branch names, too.
++It's worth mentioning that this changes your remote branch names, too.
+ What used to be referenced at `pb/master` is now at `paul/master`.
+ 
+-If you want to remove a remote for some reason -- you've moved the server or are no longer using a particular mirror, or perhaps a contributor isn't contributing anymore -- you can either use `git remote remove` or `git remote rm`:
+-
+-[source,console]
+-----
+-$ git remote remove paul
+-$ git remote
+-origin
+-----
+-
+-Once you delete the reference to a remote this way, all remote-tracking branches and configuration settings associated with that remote are also deleted.
++If you want to remove a remote for some reason – you've moved the server or are no longer using a particular mirror, or perhaps a contributor isn't contributing anymore – you can use `git remote rm`:
+diff -au ../../git/progit2/progit2/book/02-git-basics/sections/tagging.asc /tmp/book/02-git-basics/sections/tagging.asc.tmp
+--- ../../git/progit2/progit2/book/02-git-basics/sections/tagging.asc	2020-08-29 09:58:24.048195629 +0900
++++ /tmp/book/02-git-basics/sections/tagging.asc.tmp	2020-10-25 09:24:25.639965914 +0900
+@@ -1,299 +1,77 @@
+-[[_git_tagging]]
++[[r_git_tagging]]
+ === Tagging
+ 
+-(((tags)))
+-Like most VCSs, Git has the ability to tag specific points in a repository's history as being important.
+-Typically, people use this functionality to mark release points (`v1.0`, `v2.0` and so on).
+-In this section, you'll learn how to list existing tags, how to create and delete tags, and what the different types of tags are.
++Like most VCSs, Git has the ability to tag specific points in history as being important.
++Typically people use this functionality to mark release points (v1.0, and so on).
++In this section, you'll learn how to list the available tags, how to create new tags, and what the different types of tags are.
+ 
+ ==== Listing Your Tags
+ 
+-Listing the existing tags in Git is straightforward.
+-Just type `git tag` (with optional `-l` or `--list`):(((git commands, tag)))
++Listing the available tags in Git is straightforward.
++Just type `git tag`:(((git commands, tag)))
+ 
+-[source,console]
+-----
+-$ git tag
+-v1.0
+-v2.0
+-----
++This command lists the tags in alphabetical order; the order in which they appear has no real importance.
+ 
+-This command lists the tags in alphabetical order; the order in which they are displayed has no real importance.
+-
+-You can also search for tags that match a particular pattern.
++You can also search for tags with a particular pattern.
+ The Git source repo, for instance, contains more than 500 tags.
+-If you're interested only in looking at the 1.8.5 series, you can run this:
+-
+-[source,console]
+-----
+-$ git tag -l "v1.8.5*"
+-v1.8.5
+-v1.8.5-rc0
+-v1.8.5-rc1
+-v1.8.5-rc2
+-v1.8.5-rc3
+-v1.8.5.1
+-v1.8.5.2
+-v1.8.5.3
+-v1.8.5.4
+-v1.8.5.5
+-----
+-
+-[NOTE]
+-.Listing tag wildcards requires `-l` or `--list` option
+-====
+-If you want just the entire list of tags, running the command `git tag` implicitly assumes you want a listing and provides one; the use of `-l` or `--list` in this case is optional.
+-
+-If, however, you're supplying a wildcard pattern to match tag names, the use of `-l` or `--list` is mandatory.
+-====
++If you're only interested in looking at the 1.8.5 series, you can run this:
+ 
+ ==== Creating Tags
+ 
+-Git supports two types of tags: _lightweight_ and _annotated_.
++Git uses two main types of tags: lightweight and annotated.
+ 
+-A lightweight tag is very much like a branch that doesn't change -- it's just a pointer to a specific commit.
++A lightweight tag is very much like a branch that doesn't change – it's just a pointer to a specific commit.
+ 
+ Annotated tags, however, are stored as full objects in the Git database.
+ They're checksummed; contain the tagger name, email, and date; have a tagging message; and can be signed and verified with GNU Privacy Guard (GPG).
+ It's generally recommended that you create annotated tags so you can have all this information; but if you want a temporary tag or for some reason don't want to keep the other information, lightweight tags are available too.
+ 
+-[[_annotated_tags]]
+ ==== Annotated Tags
+ 
+-(((tags, annotated)))
+ Creating an annotated tag in Git is simple.
+ The easiest way is to specify `-a` when you run the `tag` command:(((git commands, tag)))
+ 
+-[source,console]
+-----
+-$ git tag -a v1.4 -m "my version 1.4"
+-$ git tag
+-v0.1
+-v1.3
+-v1.4
+-----
+-
+ The `-m` specifies a tagging message, which is stored with the tag.
+ If you don't specify a message for an annotated tag, Git launches your editor so you can type it in.
+ 
+ You can see the tag data along with the commit that was tagged by using the `git show` command:
+ 
+-[source,console]
+-----
+-$ git show v1.4
+-tag v1.4
+-Tagger: Ben Straub <[e-mail]>
+-Date:   Sat May 3 20:19:12 2014 -0700
+-
+-my version 1.4
+-
+-commit ca82a6dff817ec66f44342007202690a93763949
+-Author: Scott Chacon <[e-mail]>
+-Date:   Mon Mar 17 21:52:11 2008 -0700
+-
+-    Change version number
+-----
+-
+ That shows the tagger information, the date the commit was tagged, and the annotation message before showing the commit information.
+ 
+ ==== Lightweight Tags
+ 
+-(((tags, lightweight)))
+ Another way to tag commits is with a lightweight tag.
+-This is basically the commit checksum stored in a file -- no other information is kept.
+-To create a lightweight tag, don't supply any of the `-a`, `-s`, or `-m` options, just provide a tag name:
+-
+-[source,console]
+-----
+-$ git tag v1.4-lw
+-$ git tag
+-v0.1
+-v1.3
+-v1.4
+-v1.4-lw
+-v1.5
+-----
++This is basically the commit checksum stored in a file – no other information is kept.
++To create a lightweight tag, don't supply the `-a`, `-s`, or `-m` option:
+ 
+ This time, if you run `git show` on the tag, you don't see the extra tag information.(((git commands, show)))
+ The command just shows the commit:
+ 
+-[source,console]
+-----
+-$ git show v1.4-lw
+-commit ca82a6dff817ec66f44342007202690a93763949
+-Author: Scott Chacon <[e-mail]>
+-Date:   Mon Mar 17 21:52:11 2008 -0700
+-
+-    Change version number
+-----
+-
+ ==== Tagging Later
+ 
+ You can also tag commits after you've moved past them.
+ Suppose your commit history looks like this:
+ 
+-[source,console]
+-----
+-$ git log --pretty=oneline
+-15027957951b64cf874c3557a0f3547bd83b3ff6 Merge branch 'experiment'
+-a6b4c97498bd301d84096da251c98a07c7723e65 Create write support
+-0d52aaab4479697da7686c15f77a3d64d9165190 One more thing
+-6d52a271eda8725415634dd79daabbc4d9b6008e Merge branch 'experiment'
+-0b7434d86859cc7b8c3d5e1dddfed66ff742fcbc Add commit function
+-4682c3261057305bdd616e23b64b0857d832627b Add todo file
+-166ae0c4d3f420721acbb115cc33848dfcc2121a Create write support
+-9fceb02d0ae598e95dc970b74767f19372d61af8 Update rakefile
+-964f16d36dfccde844893cac5b347e7b3d44abbc Commit the todo
+-8a5cbc430f1a9c3d00faaeffd07798508422908a Update readme
+-----
+-
+-Now, suppose you forgot to tag the project at v1.2, which was at the ``Update rakefile'' commit.
++Now, suppose you forgot to tag the project at v1.2, which was at the ``updated rakefile'' commit.
+ You can add it after the fact.
+ To tag that commit, you specify the commit checksum (or part of it) at the end of the command:
+ 
+-[source,console]
+-----
+-$ git tag -a v1.2 9fceb02
+-----
+-
+ You can see that you've tagged the commit:(((git commands, tag)))
+ 
+-[source,console]
+-----
+-$ git tag
+-v0.1
+-v1.2
+-v1.3
+-v1.4
+-v1.4-lw
+-v1.5
+-
+-$ git show v1.2
+-tag v1.2
+-Tagger: Scott Chacon <[e-mail]>
+-Date:   Mon Feb 9 15:32:16 2009 -0800
+-
+-version 1.2
+-commit 9fceb02d0ae598e95dc970b74767f19372d61af8
+-Author: Magnus Chacon <[e-mail]>
+-Date:   Sun Apr 27 20:43:35 2008 -0700
+-
+-    Update rakefile
+-...
+-----
+-
+-[[_sharing_tags]]
+ ==== Sharing Tags
+ 
+ By default, the `git push` command doesn't transfer tags to remote servers.(((git commands, push)))
+ You will have to explicitly push tags to a shared server after you have created them.
+-This process is just like sharing remote branches -- you can run `git push origin <tagname>`.
+-
+-[source,console]
+-----
+-$ git push origin v1.5
+-Counting objects: 14, done.
+-Delta compression using up to 8 threads.
+-Compressing objects: 100% (12/12), done.
+-Writing objects: 100% (14/14), 2.05 KiB | 0 bytes/s, done.
+-Total 14 (delta 3), reused 0 (delta 0)
+-To [e-mail]:schacon/simplegit.git
+- * [new tag]         v1.5 -> v1.5
+-----
++This process is just like sharing remote branches – you can run `git push origin [tagname]`.
+ 
+ If you have a lot of tags that you want to push up at once, you can also use the `--tags` option to the `git push` command.
+ This will transfer all of your tags to the remote server that are not already there.
+ 
+-[source,console]
+-----
+-$ git push origin --tags
+-Counting objects: 1, done.
+-Writing objects: 100% (1/1), 160 bytes | 0 bytes/s, done.
+-Total 1 (delta 0), reused 0 (delta 0)
+-To [e-mail]:schacon/simplegit.git
+- * [new tag]         v1.4 -> v1.4
+- * [new tag]         v1.4-lw -> v1.4-lw
+-----
+-
+ Now, when someone else clones or pulls from your repository, they will get all your tags as well.
+ 
+-[NOTE]
+-.`git push` pushes both types of tags
+-====
+-`git push <remote> --tags` will push both lightweight and annotated tags.
+-There is currently no option to push only lightweight tags, but if you use `git push <remote> --follow-tags` only annotated tags will be pushed to the remote.
+-====
+-
+-==== Deleting Tags
+-
+-To delete a tag on your local repository, you can use `git tag -d <tagname>`.
+-For example, we could remove our lightweight tag above as follows:
+-
+-[source,console]
+-----
+-$ git tag -d v1.4-lw
+-Deleted tag 'v1.4-lw' (was e7d5add)
+-----
+-
+-Note that this does not remove the tag from any remote servers.
+-There are two common variations for deleting a tag from a remote server.
+-
+-The first variation is `git push <remote> :refs/tags/<tagname>`:
+-
+-[source,console]
+-----
+-$ git push origin :refs/tags/v1.4-lw
+-To /[e-mail]:schacon/simplegit.git
+- - [deleted]         v1.4-lw
+-----
+-
+-The way to interpret the above is to read it as the null value before the colon is being pushed to the remote tag name, effectively deleting it.
+-
+-The second (and more intuitive) way to delete a remote tag is with:
+-
+-[source,console]
+-----
+-$ git push origin --delete <tagname>
+-----
+-
+ ==== Checking out Tags
+ 
+-If you want to view the versions of files a tag is pointing to, you can do a `git checkout` of that tag, although this puts your repository in ``detached HEAD'' state, which has some ill side effects:
+-
+-[source,console]
+-----
+-$ git checkout v2.0.0
+-Note: switching to 'v2.0.0'.
+-
+-You are in 'detached HEAD' state. You can look around, make experimental
+-changes and commit them, and you can discard any commits you make in this
+-state without impacting any branches by performing another checkout.
+-
+-If you want to create a new branch to retain commits you create, you may
+-do so (now or later) by using -c with the switch command. Example:
+-
+-  git switch -c <new-branch-name>
+-
+-Or undo this operation with:
+-
+-  git switch -
+-
+-Turn off this advice by setting config variable advice.detachedHead to false
+-
+-HEAD is now at 99ada87... Merge pull request #89 from schacon/appendix-final
+-
+-$ git checkout v2.0-beta-0.1
+-Previous HEAD position was 99ada87... Merge pull request #89 from schacon/appendix-final
+-HEAD is now at df3f601... Add atlas.json and cover image
+-----
+-
+-In ``detached HEAD'' state, if you make changes and then create a commit, the tag will stay the same, but your new commit won't belong to any branch and will be unreachable, except by the exact commit hash.
+-Thus, if you need to make changes -- say you're fixing a bug on an older version, for instance -- you will generally want to create a branch:
+-
+-[source,console]
+-----
+-$ git checkout -b version2 v2.0.0
+-Switched to a new branch 'version2'
+-----
++You can't really check out a tag in Git, since they can't be moved around.
++If you want to put a version of your repository in your working directory that looks like a specific tag, you can create a new branch at a specific tag with  `git checkout -b [branchname] [tagname]`:
+ 
+-If you do this and make a commit, your `version2` branch will be slightly different than your `v2.0.0` tag since it will move forward with your new changes, so do be careful.
++Of course if you do this and do a commit, your `version2` branch will be slightly different than your `v2.0.0` tag since it will move forward with your new changes, so do be careful.
+diff -au ../../git/progit2/progit2/book/02-git-basics/sections/undoing.asc /tmp/book/02-git-basics/sections/undoing.asc.tmp
+--- ../../git/progit2/progit2/book/02-git-basics/sections/undoing.asc	2020-10-18 09:42:35.779991668 +0900
++++ /tmp/book/02-git-basics/sections/undoing.asc.tmp	2020-10-25 09:24:25.644966150 +0900
+@@ -1,4 +1,4 @@
+-[[_undoing]]
++[[r_undoing]]
+ === Undoing Things
+ 
+ At any stage, you may want to undo something.
+@@ -7,12 +7,7 @@
+ This is one of the few areas in Git where you may lose some work if you do it wrong.
+ 
+ One of the common undos takes place when you commit too early and possibly forget to add some files, or you mess up your commit message.
+-If you want to redo that commit, make the additional changes you forgot, stage them, and commit again using the `--amend` option:
+-
+-[source,console]
+-----
+-$ git commit --amend
+-----
++If you want to try that commit again, you can run commit with the `--amend` option:
+ 
+ This command takes your staging area and uses it for the commit.
+ If you've made no changes since your last commit (for instance, you run this command immediately after your previous commit), then your snapshot will look exactly the same, and all you'll change is your commit message.
+@@ -22,214 +17,50 @@
+ 
+ As an example, if you commit and then realize you forgot to stage the changes in a file you wanted to add to this commit, you can do something like this:
+ 
+-[source,console]
+-----
+-$ git commit -m 'Initial commit'
+-$ git add forgotten_file
+-$ git commit --amend
+-----
+-
+-You end up with a single commit -- the second commit replaces the results of the first.
+-
+-[NOTE]
+-====
+-It's important to understand that when you're amending your last commit, you're not so much fixing it as _replacing_ it entirely with a new, improved commit that pushes the old commit out of the way and puts the new commit in its place.
+-Effectively, it's as if the previous commit never happened, and it won't show up in your repository history.
+-
+-The obvious value to amending commits is to make minor improvements to your last commit, without cluttering your repository history with commit messages of the form, ``Oops, forgot to add a file'' or ``Darn, fixing a typo in last commit''.
+-====
+-
+-[NOTE]
+-====
+-Only amend commits that are still local and have not been pushed somewhere.
+-Amending previously pushed commits and force pushing the branch will cause problems for your collaborators.
+-For more on what happens when you do this and how to recover if you're on the receiving end read <<_rebase_peril>>.
+-====
++You end up with a single commit – the second commit replaces the results of the first.
+ 
+-[[_unstaging]]
+ ==== Unstaging a Staged File
+ 
+-The next two sections demonstrate how to work with your staging area and working directory changes.
++The next two sections demonstrate how to wrangle your staging area and working directory changes.
+ The nice part is that the command you use to determine the state of those two areas also reminds you how to undo changes to them.
+ For example, let's say you've changed two files and want to commit them as two separate changes, but you accidentally type `git add *` and stage them both.
+ How can you unstage one of the two?
+ The `git status` command reminds you:
+ 
+-[source,console]
+-----
+-$ git add *
+-$ git status
+-On branch master
+-Changes to be committed:
+-  (use "git reset HEAD <file>..." to unstage)
+-
+-    renamed:    README.md -> README
+-    modified:   CONTRIBUTING.md
+-----
+-
+ Right below the ``Changes to be committed'' text, it says use `git reset HEAD <file>...` to unstage.
+ So, let's use that advice to unstage the `CONTRIBUTING.md` file:
+ 
+-[source,console]
+-----
+-$ git reset HEAD CONTRIBUTING.md
+-Unstaged changes after reset:
+-M	CONTRIBUTING.md
+-$ git status
+-On branch master
+-Changes to be committed:
+-  (use "git reset HEAD <file>..." to unstage)
+-
+-    renamed:    README.md -> README
+-
+-Changes not staged for commit:
+-  (use "git add <file>..." to update what will be committed)
+-  (use "git checkout -- <file>..." to discard changes in working directory)
+-
+-    modified:   CONTRIBUTING.md
+-----
+-
+ The command is a bit strange, but it works.
+ The `CONTRIBUTING.md` file is modified but once again unstaged.
+ 
+-[NOTE]
+ =====
+-It's true that `git reset` can be a dangerous command, especially if you provide the `--hard` flag.
+-However, in the scenario described above, the file in your working directory is not touched, so it's relatively safe.
++While `git reset` _can_ be a dangerous command if you call it with `--hard`, in this instance the file in your working directory is not touched.
++Calling `git reset` without an option is not dangerous - it only touches your staging area.
+ =====
+ 
+ For now this magic invocation is all you need to know about the `git reset` command.
+-We'll go into much more detail about what `reset` does and how to master it to do really interesting things in <<ch07-git-tools#_git_reset>>.
++We'll go into much more detail about what `reset` does and how to master it to do really interesting things in <<ch07-git-tools#r_git_reset>>.
+ 
+ ==== Unmodifying a Modified File
+ 
+ What if you realize that you don't want to keep your changes to the `CONTRIBUTING.md` file?
+-How can you easily unmodify it -- revert it back to what it looked like when you last committed (or initially cloned, or however you got it into your working directory)?
++How can you easily unmodify it – revert it back to what it looked like when you last committed (or initially cloned, or however you got it into your working directory)?
+ Luckily, `git status` tells you how to do that, too.
+ In the last example output, the unstaged area looks like this:
+ 
+-[source,console]
+-----
+-Changes not staged for commit:
+-  (use "git add <file>..." to update what will be committed)
+-  (use "git checkout -- <file>..." to discard changes in working directory)
+-
+-    modified:   CONTRIBUTING.md
+-----
+-
+ It tells you pretty explicitly how to discard the changes you've made.
+ Let's do what it says:
+ 
+-[source,console]
+-----
+-$ git checkout -- CONTRIBUTING.md
+-$ git status
+-On branch master
+-Changes to be committed:
+-  (use "git reset HEAD <file>..." to unstage)
+-
+-    renamed:    README.md -> README
+-
+-----
+-
+ You can see that the changes have been reverted.
+ 
+-[IMPORTANT]
+ =====
+ It's important to understand that `git checkout -- <file>` is a dangerous command.
+-Any local changes you made to that file are gone -- Git just replaced that file with the most recently-committed version.
+-Don't ever use this command unless you absolutely know that you don't want those unsaved local changes.
++Any changes you made to that file are gone – you just copied another file over it.
++Don't ever use this command unless you absolutely know that you don't want the file.
+ =====
+ 
+ If you would like to keep the changes you've made to that file but still need to get it out of the way for now, we'll go over stashing and branching in <<ch03-git-branching#ch03-git-branching>>; these are generally better ways to go.
+ 
+ Remember, anything that is _committed_ in Git can almost always be recovered.
+-Even commits that were on branches that were deleted or commits that were overwritten with an `--amend` commit can be recovered (see <<ch10-git-internals#_data_recovery>> for data recovery).
++Even commits that were on branches that were deleted or commits that were overwritten with an `--amend` commit can be recovered (see <<ch10-git-internals#r_data_recovery>> for data recovery).
+ However, anything you lose that was never committed is likely never to be seen again.
+-
+-[[undoing_git_restore]]
+-==== Undoing things with git restore
+-
+-Git version 2.25.0 introduced a new command: `git restore`.
+-It's basically an alternative to `git reset` which we just covered.
+-From Git version 2.25.0 onwards, Git will use `git restore` instead of `git reset` for many undo operations.
+-
+-Let's retrace our steps, and undo things with `git restore` instead of `git reset`.
+-
+-===== Unstaging a Staged File with git restore
+-
+-The next two sections demonstrate how to work with your staging area and working directory changes with `git restore`.
+-The nice part is that the command you use to determine the state of those two areas also reminds you how to undo changes to them.
+-For example, let's say you've changed two files and want to commit them as two separate changes, but you accidentally type `git add *` and stage them both.
+-How can you unstage one of the two?
+-The `git status` command reminds you:
+-
+-[source,console]
+-----
+-$ git add *
+-$ git status
+-On branch master
+-Changes to be committed:
+-  (use "git restore --staged <file>..." to unstage)
+-	modified:   CONTRIBUTING.md
+-	renamed:    README.md -> README
+-
+-----
+-
+-Right below the ``Changes to be committed'' text, it says use `git restore --staged <file>...` to unstage.
+-So, let's use that advice to unstage the `CONTRIBUTING.md` file:
+-
+-[source,console]
+-----
+-$ git restore --staged CONTRIBUTING.md
+-$ git status
+-On branch master
+-Changes to be committed:
+-  (use "git restore --staged <file>..." to unstage)
+-	renamed:    README.md -> README
+-
+-Changes not staged for commit:
+-  (use "git add <file>..." to update what will be committed)
+-  (use "git restore <file>..." to discard changes in working directory)
+-	modified:   CONTRIBUTING.md
+-
+-----
+-
+-The `CONTRIBUTING.md` file is modified but once again unstaged.
+-
+-===== Unmodifying a Modified File with git restore
+-
+-What if you realize that you don't want to keep your changes to the `CONTRIBUTING.md` file?
+-How can you easily unmodify it -- revert it back to what it looked like when you last committed (or initially cloned, or however you got it into your working directory)?
+-Luckily, `git status` tells you how to do that, too.
+-In the last example output, the unstaged area looks like this:
+-
+-[source,console]
+-----
+-Changes not staged for commit:
+-  (use "git add <file>..." to update what will be committed)
+-  (use "git restore <file>..." to discard changes in working directory)
+-	modified:   CONTRIBUTING.md
+-
+-----
+-
+-It tells you pretty explicitly how to discard the changes you've made.
+-Let's do what it says:
+-
+-[source,console]
+-----
+-$ git restore CONTRIBUTING.md
+-$ git status
+-On branch master
+-Changes to be committed:
+-  (use "git restore --staged <file>..." to unstage)
+-	renamed:    README.md -> README
+-
+-----
+-
+-[IMPORTANT]
+-=====
+-It's important to understand that `git restore <file>` is a dangerous command.
+-Any local changes you made to that file are gone -- Git just replaced that file with the most recently-committed version.
+-Don't ever use this command unless you absolutely know that you don't want those unsaved local changes.
+-=====
+diff -au ../../git/progit2/progit2/book/02-git-basics/sections/viewing-history.asc /tmp/book/02-git-basics/sections/viewing-history.asc.tmp
+--- ../../git/progit2/progit2/book/02-git-basics/sections/viewing-history.asc	2020-09-26 08:56:07.950296410 +0900
++++ /tmp/book/02-git-basics/sections/viewing-history.asc.tmp	2020-10-25 09:24:25.649966386 +0900
+@@ -1,213 +1,76 @@
+-[[_viewing_history]]
++[[r_viewing_history]]
+ === Viewing the Commit History
+ 
+ After you have created several commits, or if you have cloned a repository with an existing commit history, you'll probably want to look back to see what has happened.
+ The most basic and powerful tool to do this is the `git log` command.
+ 
+ These examples use a very simple project called ``simplegit''.
+-To get the project, run:
+-
+-[source,console]
+-----
+-$ git clone https://github.com/schacon/simplegit-progit
+-----
++To get the project, run
+ 
+ When you run `git log` in this project, you should get output that looks something like this:(((git commands, log)))
+ 
+-[source,console]
+-----
+-$ git log
+-commit ca82a6dff817ec66f44342007202690a93763949
+-Author: Scott Chacon <[e-mail]>
+-Date:   Mon Mar 17 21:52:11 2008 -0700
+-
+-    Change version number
+-
+-commit 085bb3bcb608e1e8451d4b2432f8ecbe6306e7e7
+-Author: Scott Chacon <[e-mail]>
+-Date:   Sat Mar 15 16:40:33 2008 -0700
+-
+-    Remove unnecessary test
+-
+-commit a11bef06a3f659402fe7563abf99ad00de2209e6
+-Author: Scott Chacon <[e-mail]>
+-Date:   Sat Mar 15 10:31:28 2008 -0700
+-
+-    Initial commit
+-----
+-
+-By default, with no arguments, `git log` lists the commits made in that repository in reverse chronological order; that is, the most recent commits show up first.
++By default, with no arguments, `git log` lists the commits made in that repository in reverse chronological order – that is, the most recent commits show up first.
+ As you can see, this command lists each commit with its SHA-1 checksum, the author's name and email, the date written, and the commit message.
+ 
+ A huge number and variety of options to the `git log` command are available to show you exactly what you're looking for.
+ Here, we'll show you some of the most popular.
+ 
+-One of the more helpful options is `-p` or `--patch`, which shows the difference (the _patch_ output) introduced in each commit.
+-You can also limit the number of log entries displayed, such as using `-2` to show only the last two entries.
+-
+-[source,console]
+-----
+-$ git log -p -2
+-commit ca82a6dff817ec66f44342007202690a93763949
+-Author: Scott Chacon <[e-mail]>
+-Date:   Mon Mar 17 21:52:11 2008 -0700
+-
+-    Change version number
+-
+-diff --git a/Rakefile b/Rakefile
+-index a874b73..8f94139 100644
+---- a/Rakefile
+-+++ b/Rakefile
+-@@ -5,7 +5,7 @@ require 'rake/gempackagetask'
+- spec = Gem::Specification.new do |s|
+-     s.platform  =   Gem::Platform::RUBY
+-     s.name      =   "simplegit"
+--    s.version   =   "0.1.0"
+-+    s.version   =   "0.1.1"
+-     s.author    =   "Scott Chacon"
+-     s.email     =   "[e-mail]"
+-     s.summary   =   "A simple gem for using Git in Ruby code."
+-
+-commit 085bb3bcb608e1e8451d4b2432f8ecbe6306e7e7
+-Author: Scott Chacon <[e-mail]>
+-Date:   Sat Mar 15 16:40:33 2008 -0700
+-
+-    Remove unnecessary test
+-
+-diff --git a/lib/simplegit.rb b/lib/simplegit.rb
+-index a0a60ae..47c6340 100644
+---- a/lib/simplegit.rb
+-+++ b/lib/simplegit.rb
+-@@ -18,8 +18,3 @@ class SimpleGit
+-     end
+-
+- end
+--
+--if $0 == __FILE__
+--  git = SimpleGit.new
+--  puts git.show
+--end
+-----
++One of the more helpful options is `-p`, which shows the difference introduced in each commit.
++You can also use `-2`, which limits the output to only the last two entries:
+ 
+ This option displays the same information but with a diff directly following each entry.
+ This is very helpful for code review or to quickly browse what happened during a series of commits that a collaborator has added.
+ You can also use a series of summarizing options with `git log`.
+ For example, if you want to see some abbreviated stats for each commit, you can use the `--stat` option:
+ 
+-[source,console]
+-----
+-$ git log --stat
+-commit ca82a6dff817ec66f44342007202690a93763949
+-Author: Scott Chacon <[e-mail]>
+-Date:   Mon Mar 17 21:52:11 2008 -0700
+-
+-    Change version number
+-
+- Rakefile | 2 +-
+- 1 file changed, 1 insertion(+), 1 deletion(-)
+-
+-commit 085bb3bcb608e1e8451d4b2432f8ecbe6306e7e7
+-Author: Scott Chacon <[e-mail]>
+-Date:   Sat Mar 15 16:40:33 2008 -0700
+-
+-    Remove unnecessary test
+-
+- lib/simplegit.rb | 5 -----
+- 1 file changed, 5 deletions(-)
+-
+-commit a11bef06a3f659402fe7563abf99ad00de2209e6
+-Author: Scott Chacon <[e-mail]>
+-Date:   Sat Mar 15 10:31:28 2008 -0700
+-
+-    Initial commit
+-
+- README           |  6 ++++++
+- Rakefile         | 23 +++++++++++++++++++++++
+- lib/simplegit.rb | 25 +++++++++++++++++++++++++
+- 3 files changed, 54 insertions(+)
+-----
+-
+ As you can see, the `--stat` option prints below each commit entry a list of modified files, how many files were changed, and how many lines in those files were added and removed.
+ It also puts a summary of the information at the end.
+ 
+ Another really useful option is `--pretty`.
+ This option changes the log output to formats other than the default.
+-A few prebuilt option values are available for you to use.
+-The `oneline` value for this option prints each commit on a single line, which is useful if you're looking at a lot of commits.
+-In addition, the `short`, `full`, and `fuller` values show the output in roughly the same format but with less or more information, respectively:
+-
+-[source,console]
+-----
+-$ git log --pretty=oneline
+-ca82a6dff817ec66f44342007202690a93763949 Change version number
+-085bb3bcb608e1e8451d4b2432f8ecbe6306e7e7 Remove unnecessary test
+-a11bef06a3f659402fe7563abf99ad00de2209e6 Initial commit
+-----
+-
+-The most interesting option value is `format`, which allows you to specify your own log output format.
+-This is especially useful when you're generating output for machine parsing -- because you specify the format explicitly, you know it won't change with updates to Git:(((log formatting)))
+-
+-[source,console]
+-----
+-$ git log --pretty=format:"%h - %an, %ar : %s"
+-ca82a6d - Scott Chacon, 6 years ago : Change version number
+-085bb3b - Scott Chacon, 6 years ago : Remove unnecessary test
+-a11bef0 - Scott Chacon, 6 years ago : Initial commit
+-----
++A few prebuilt options are available for you to use.
++The `oneline` option prints each commit on a single line, which is useful if you're looking at a lot of commits.
++In addition, the `short`, `full`, and `fuller` options show the output in roughly the same format but with less or more information, respectively:
+ 
+-<<pretty_format>> lists some of the more useful specifiers that `format` takes.
++The most interesting option is `format`, which allows you to specify your own log output format.
++This is especially useful when you're generating output for machine parsing – because you specify the format explicitly, you know it won't change with updates to Git:(((log formatting)))
+ 
+-[[pretty_format]]
+-.Useful specifiers for `git log --pretty=format`
++<<rpretty_format>> lists some of the more useful options that format takes.
++
++.Useful options for `git log --pretty=format`
+ [cols="1,4",options="header"]
+ |================================
+-| Specifier | Description of Output
+-| `%H`      | Commit hash
+-| `%h`      | Abbreviated commit hash
+-| `%T`      | Tree hash
+-| `%t`      | Abbreviated tree hash
+-| `%P`      | Parent hashes
+-| `%p`      | Abbreviated parent hashes
+-| `%an`     | Author name
+-| `%ae`     | Author email
+-| `%ad`     | Author date (format respects the --date=option)
+-| `%ar`     | Author date, relative
+-| `%cn`     | Committer name
+-| `%ce`     | Committer email
+-| `%cd`     | Committer date
+-| `%cr`     | Committer date, relative
+-| `%s`      | Subject
++| Option   | Description of Output
++| `%H`     | Commit hash
++| `%h`     | Abbreviated commit hash
++| `%T`     | Tree hash
++| `%t`     | Abbreviated tree hash
++| `%P`     | Parent hashes
++| `%p`     | Abbreviated parent hashes
++| `%an`    | Author name
++| `%ae`    | Author email
++| `%ad`    | Author date (format respects the --date=option)
++| `%ar`    | Author date, relative
++| `%cn`    | Committer name
++| `%ce`    | Committer email
++| `%cd`    | Committer date
++| `%cr`    | Committer date, relative
++| `%s`     | Subject
+ |================================
+ 
+ You may be wondering what the difference is between _author_ and _committer_.
+ The author is the person who originally wrote the work, whereas the committer is the person who last applied the work.
+-So, if you send in a patch to a project and one of the core members applies the patch, both of you get credit -- you as the author, and the core member as the committer.
++So, if you send in a patch to a project and one of the core members applies the patch, both of you get credit – you as the author, and the core member as the committer.
+ We'll cover this distinction a bit more in <<ch05-distributed-git#ch05-distributed-git>>.
+ 
+-The `oneline` and `format` option values are particularly useful with another `log` option called `--graph`.
++The `oneline` and `format` options are particularly useful with another `log` option called `--graph`.
+ This option adds a nice little ASCII graph showing your branch and merge history:
+ 
+-[source,console]
+-----
+-$ git log --pretty=format:"%h %s" --graph
+-* 2d3acf9 Ignore errors from SIGCHLD on trap
+-*  5e3ee11 Merge branch 'master' of git://github.com/dustin/grit
+-|\
+-| * 420eac9 Add method for getting the current branch
+-* | 30e367c Timeout code and tests
+-* | 5a09431 Add timeout protection to grit
+-* | e1193f8 Support for heads with slashes in them
+-|/
+-* d6016bc Require time for xmlschema
+-*  11d191e Merge branch 'defunkt' into local
+-----
+-
+ This type of output will become more interesting as we go through branching and merging in the next chapter.
+ 
+-Those are only some simple output-formatting options to `git log` -- there are many more.
+-<<log_options>> lists the options we've covered so far, as well as some other common formatting options that may be useful, along with how they change the output of the log command.
++Those are only some simple output-formatting options to `git log` – there are many more.
++<<rlog_options>> lists the options we've covered so far, as well as some other common formatting options that may be useful, along with how they change the output of the log command.
+ 
+-[[log_options]]
+ .Common options to `git log`
+ [cols="1,4",options="header"]
+ |================================
+@@ -220,63 +83,39 @@
+ | `--abbrev-commit` | Show only the first few characters of the SHA-1 checksum instead of all 40.
+ | `--relative-date` | Display the date in a relative format (for example, ``2 weeks ago'') instead of using the full date format.
+ | `--graph`         | Display an ASCII graph of the branch and merge history beside the log output.
+-| `--pretty`        | Show commits in an alternate format. Option values include oneline, short, full, fuller, and format (where you specify your own format).
+-| `--oneline`       | Shorthand for `--pretty=oneline --abbrev-commit` used together.
++| `--pretty`        | Show commits in an alternate format. Options include oneline, short, full, fuller, and format (where you specify your own format).
+ |================================
+ 
+ ==== Limiting Log Output
+ 
+-In addition to output-formatting options, `git log` takes a number of useful limiting options; that is, options that let you show only a subset of commits.
+-You've seen one such option already -- the `-2` option, which displays only the last two commits.
++In addition to output-formatting options, `git log` takes a number of useful limiting options – that is, options that let you show only a subset of commits.
++You've seen one such option already – the `-2` option, which show only the last two commits.
+ In fact, you can do `-<n>`, where `n` is any integer to show the last `n` commits.
+ In reality, you're unlikely to use that often, because Git by default pipes all output through a pager so you see only one page of log output at a time.
+ 
+ However, the time-limiting options such as `--since` and `--until` are very useful.
+ For example, this command gets the list of commits made in the last two weeks:
+ 
+-[source,console]
+-----
+-$ git log --since=2.weeks
+-----
+-
+-This command works with lots of formats -- you can specify a specific date like `"2008-01-15"`, or a relative date such as `"2 years 1 day 3 minutes ago"`.
++This command works with lots of formats – you can specify a specific date like `"2008-01-15"`, or a relative date such as `"2 years 1 day 3 minutes ago"`.
+ 
+ You can also filter the list to commits that match some search criteria.
+ The `--author` option allows you to filter on a specific author, and the `--grep` option lets you search for keywords in the commit messages.
++(Note that if you want to specify both author and grep options, you have to add `--all-match` or the command will match commits with either.)
+ 
+-[NOTE]
+-====
+-You can specify more than one instance of both the `--author` and `--grep` search criteria, which
+-will limit the commit output to commits that match _any_ of the `--author` patterns and _any_
+-of the `--grep` patterns; however, adding the `--all-match` option further limits the output to
+-just those commits that match _all_ `--grep` patterns.
+-====
+-
+-Another really helpful filter is the `-S` option (colloquially referred to as Git's ``pickaxe'' option), which takes a string and shows only those commits that changed the number of occurrences of that string.
++Another really helpful filter is the `-S` option which takes a string and only shows the commits that introduced a change to the code that added or removed that string.
+ For instance, if you wanted to find the last commit that added or removed a reference to a specific function, you could call:
+ 
+-[source,console]
+-----
+-$ git log -S function_name
+-----
+-
+ The last really useful option to pass to `git log` as a filter is a path.
+ If you specify a directory or file name, you can limit the log output to commits that introduced a change to those files.
+-This is always the last option and is generally preceded by double dashes (`--`) to separate the paths from the options:
+-
+-[source,console]
+-----
+-$ git log -- path/to/file
+-----
++This is always the last option and is generally preceded by double dashes (`--`) to separate the paths from the options.
+ 
+-In <<limit_options>> we'll list these and a few other common options for your reference.
++In <<rlimit_options>> we'll list these and a few other common options for your reference.
+ 
+-[[limit_options]]
+ .Options to limit the output of `git log`
+ [cols="2,4",options="header"]
+ |================================
+ | Option                | Description
+-| `-<n>`                | Show only the last n commits
++| `-(n)`                | Show only the last n commits
+ | `--since`, `--after`  | Limit the commits to those made after the specified date.
+ | `--until`, `--before` | Limit the commits to those made before the specified date.
+ | `--author`            | Only show commits in which the author entry matches the specified string.
+@@ -285,25 +124,6 @@
+ | `-S`                  | Only show commits adding or removing code matching the string
+ |================================
+ 
+-For example, if you want to see which commits modifying test files in the Git source code history were committed by Junio Hamano in the month of October 2008 and are not merge commits, you can run something like this:(((log filtering)))
+-
+-[source,console]
+-----
+-$ git log --pretty="%h - %s" --author='Junio C Hamano' --since="2008-10-01" \
+-   --before="2008-11-01" --no-merges -- t/
+-5610e3b - Fix testcase failure when extended attributes are in use
+-acd3b9e - Enhance hold_lock_file_for_{update,append}() API
+-f563754 - demonstrate breakage of detached checkout with symbolic link HEAD
+-d1a43f2 - reset --hard/read-tree --reset -u: remove unmerged new paths
+-51a94af - Fix "checkout --track -b newbranch" on detached HEAD
+-b0ad11e - pull: allow "git pull origin $something:$current_branch" into an unborn branch
+-----
++For example, if you want to see which commits modifying test files in the Git source code history are merged and were committed by Junio Hamano in the month of October 2008, you can run something like this:(((log filtering)))
+ 
+ Of the nearly 40,000 commits in the Git source code history, this command shows the 6 that match those criteria.
+-
+-[TIP]
+-.Preventing the display of merge commits
+-====
+-Depending on the workflow used in your repository, it's possible that a sizable percentage of the commits in your log history are just merge commits, which typically aren't very informative.
+-To prevent the display of merge commits cluttering up your log history, simply add the log option `--no-merges`.
+-====
+diff -au ../../git/progit2/progit2/book/03-git-branching/sections/basic-branching-and-merging.asc /tmp/book/03-git-branching/sections/basic-branching-and-merging.asc.tmp
+--- ../../git/progit2/progit2/book/03-git-branching/sections/basic-branching-and-merging.asc	2020-07-04 16:36:46.720685416 +0900
++++ /tmp/book/03-git-branching/sections/basic-branching-and-merging.asc.tmp	2020-10-25 09:24:25.655966668 +0900
+@@ -3,8 +3,8 @@
+ Let's go through a simple example of branching and merging with a workflow that you might use in the real world.
+ You'll follow these steps:
+ 
+-. Do some work on a website.
+-. Create a branch for a new user story you're working on.
++. Do work on a web site.
++. Create a branch for a new story you're working on.
+ . Do some work in that branch.
+ 
+ At this stage, you'll receive a call that another issue is critical and you need a hotfix.
+@@ -13,306 +13,134 @@
+ . Switch to your production branch.
+ . Create a branch to add the hotfix.
+ . After it's tested, merge the hotfix branch, and push to production.
+-. Switch back to your original user story and continue working.
++. Switch back to your original story and continue working.
+ 
+-[[_basic_branching]]
+ ==== Basic Branching
+ 
+-(((branches, basic workflow)))
+-First, let's say you're working on your project and have a couple of commits already on the `master` branch.
++First, let's say you're working on your project and have a couple of commits already.
+ 
+ .A simple commit history
+-image::images/basic-branching-1.png[A simple commit history]
++image::images/basic-branching-1.png[A simple commit history.]
+ 
+ You've decided that you're going to work on issue #53 in whatever issue-tracking system your company uses.
+-To create a new branch and switch to it at the same time, you can run the `git checkout` command with the `-b` switch:
+-
+-[source,console]
+-----
+-$ git checkout -b iss53
+-Switched to a new branch "iss53"
+-----
++To create a branch and switch to it at the same time, you can run the `git checkout` command with the `-b` switch:
+ 
+ This is shorthand for:
+ 
+-[source,console]
+-----
+-$ git branch iss53
+-$ git checkout iss53
+-----
+-
+ .Creating a new branch pointer
+-image::images/basic-branching-2.png[Creating a new branch pointer]
++image::images/basic-branching-2.png[Creating a new branch pointer.]
+ 
+-You work on your website and do some commits.
++You work on your web site and do some commits.
+ Doing so moves the `iss53` branch forward, because you have it checked out (that is, your `HEAD` is pointing to it):
+ 
+-[source,console]
+-----
+-$ vim index.html
+-$ git commit -a -m 'Create new footer [issue 53]'
+-----
+-
+-.The `iss53` branch has moved forward with your work
+-image::images/basic-branching-3.png[The `iss53` branch has moved forward with your work]
++.The iss53 branch has moved forward with your work
++image::images/basic-branching-3.png[The iss53 branch has moved forward with your work.]
+ 
+-Now you get the call that there is an issue with the website, and you need to fix it immediately.
++Now you get the call that there is an issue with the web site, and you need to fix it immediately.
+ With Git, you don't have to deploy your fix along with the `iss53` changes you've made, and you don't have to put a lot of effort into reverting those changes before you can work on applying your fix to what is in production.
+ All you have to do is switch back to your `master` branch.
+ 
+ However, before you do that, note that if your working directory or staging area has uncommitted changes that conflict with the branch you're checking out, Git won't let you switch branches.
+ It's best to have a clean working state when you switch branches.
+-There are ways to get around this (namely, stashing and commit amending) that we'll cover later on, in <<ch07-git-tools#_git_stashing>>.
++There are ways to get around this (namely, stashing and commit amending) that we'll cover later on, in <<ch07-git-tools#r_git_stashing>>.
+ For now, let's assume you've committed all your changes, so you can switch back to your `master` branch:
+ 
+-[source,console]
+-----
+-$ git checkout master
+-Switched to branch 'master'
+-----
+-
+ At this point, your project working directory is exactly the way it was before you started working on issue #53, and you can concentrate on your hotfix.
+ This is an important point to remember: when you switch branches, Git resets your working directory to look like it did the last time you committed on that branch.
+ It adds, removes, and modifies files automatically to make sure your working copy is what the branch looked like on your last commit to it.
+ 
+ Next, you have a hotfix to make.
+-Let's create a `hotfix` branch on which to work until it's completed:
+-
+-[source,console]
+-----
+-$ git checkout -b hotfix
+-Switched to a new branch 'hotfix'
+-$ vim index.html
+-$ git commit -a -m 'Fix broken email address'
+-[hotfix 1fb7853] Fix broken email address
+- 1 file changed, 2 insertions(+)
+-----
++Let's create a hotfix branch on which to work until it's completed:
+ 
+ .Hotfix branch based on `master`
+-image::images/basic-branching-4.png[Hotfix branch based on `master`]
++image::images/basic-branching-4.png[Hotfix branch based on `master`.]
+ 
+-You can run your tests, make sure the hotfix is what you want, and finally merge the `hotfix` branch back into your `master` branch to deploy to production.
++You can run your tests, make sure the hotfix is what you want, and merge it back into your `master` branch to deploy to production.
+ You do this with the `git merge` command:(((git commands, merge)))
+ 
+-[source,console]
+-----
+-$ git checkout master
+-$ git merge hotfix
+-Updating f42c576..3a0874c
+-Fast-forward
+- index.html | 2 ++
+- 1 file changed, 2 insertions(+)
+-----
+-
+ You'll notice the phrase ``fast-forward'' in that merge.
+-Because the commit `C4` pointed to by the branch `hotfix` you merged in was directly ahead of the commit `C2` you're on, Git simply moves the pointer forward.
+-To phrase that another way, when you try to merge one commit with a commit that can be reached by following the first commit's history, Git simplifies things by moving the pointer forward because there is no divergent work to merge together -- this is called a ``fast-forward.''
++Because the commit pointed to by the branch you merged in was directly upstream of the commit you're on, Git simply moves the pointer forward.
++To phrase that another way, when you try to merge one commit with a commit that can be reached by following the first commit's history, Git simplifies things by moving the pointer forward because there is no divergent work to merge together – this is called a ``fast-forward.''
+ 
+ Your change is now in the snapshot of the commit pointed to by the `master` branch, and you can deploy the fix.
+ 
+ .`master` is fast-forwarded to `hotfix`
+-image::images/basic-branching-5.png[`master` is fast-forwarded to `hotfix`]
++image::images/basic-branching-5.png[`master` is fast-forwarded to `hotfix`.]
+ 
+ After your super-important fix is deployed, you're ready to switch back to the work you were doing before you were interrupted.
+-However, first you'll delete the `hotfix` branch, because you no longer need it -- the `master` branch points at the same place.
++However, first you'll delete the `hotfix` branch, because you no longer need it – the `master` branch points at the same place.
+ You can delete it with the `-d` option to `git branch`:
+ 
+-[source,console]
+-----
+-$ git branch -d hotfix
+-Deleted branch hotfix (3a0874c).
+-----
+-
+ Now you can switch back to your work-in-progress branch on issue #53 and continue working on it.
+ 
+-[source,console]
+-----
+-$ git checkout iss53
+-Switched to branch "iss53"
+-$ vim index.html
+-$ git commit -a -m 'Finish the new footer [issue 53]'
+-[iss53 ad82d7a] Finish the new footer [issue 53]
+-1 file changed, 1 insertion(+)
+-----
+-
+ .Work continues on `iss53`
+-image::images/basic-branching-6.png[Work continues on `iss53`]
++image::images/basic-branching-6.png[Work continues on `iss53`.]
+ 
+ It's worth noting here that the work you did in your `hotfix` branch is not contained in the files in your `iss53` branch.
+ If you need to pull it in, you can merge your `master` branch into your `iss53` branch by running `git merge master`, or you can wait to integrate those changes until you decide to pull the `iss53` branch back into `master` later.
+ 
+-[[_basic_merging]]
+ ==== Basic Merging
+ 
+-(((branches, merging)))(((merging)))
+ Suppose you've decided that your issue #53 work is complete and ready to be merged into your `master` branch.
+ In order to do that, you'll merge your `iss53` branch into `master`, much like you merged your `hotfix` branch earlier.
+ All you have to do is check out the branch you wish to merge into and then run the `git merge` command:
+ 
+-[source,console]
+-----
+-$ git checkout master
+-Switched to branch 'master'
+-$ git merge iss53
+-Merge made by the 'recursive' strategy.
+-index.html |    1 +
+-1 file changed, 1 insertion(+)
+-----
+-
+ This looks a bit different than the `hotfix` merge you did earlier.
+ In this case, your development history has diverged from some older point.
+ Because the commit on the branch you're on isn't a direct ancestor of the branch you're merging in, Git has to do some work.
+ In this case, Git does a simple three-way merge, using the two snapshots pointed to by the branch tips and the common ancestor of the two.
+ 
+ .Three snapshots used in a typical merge
+-image::images/basic-merging-1.png[Three snapshots used in a typical merge]
++image::images/basic-merging-1.png[Three snapshots used in a typical merge.]
+ 
+ Instead of just moving the branch pointer forward, Git creates a new snapshot that results from this three-way merge and automatically creates a new commit that points to it.
+ This is referred to as a merge commit, and is special in that it has more than one parent.
+ 
+ .A merge commit
+-image::images/basic-merging-2.png[A merge commit]
++image::images/basic-merging-2.png[A merge commit.]
+ 
+-Now that your work is merged in, you have no further need for the `iss53` branch.
+-You can close the issue in your issue-tracking system, and delete the branch:
++It's worth pointing out that Git determines the best common ancestor to use for its merge base; this is different than older tools like CVS or Subversion (before version 1.5), where the developer doing the merge had to figure out the best merge base for themselves.
++This makes merging a heck of a lot easier in Git than in these other systems.
+ 
+-[source,console]
+-----
+-$ git branch -d iss53
+-----
++Now that your work is merged in, you have no further need for the `iss53` branch.
++You can close the ticket in your ticket-tracking system, and delete the branch:
+ 
+-[[_basic_merge_conflicts]]
+ ==== Basic Merge Conflicts
+ 
+-(((merging, conflicts)))
+ Occasionally, this process doesn't go smoothly.
+-If you changed the same part of the same file differently in the two branches you're merging, Git won't be able to merge them cleanly.
+-If your fix for issue #53 modified the same part of a file as the `hotfix` branch, you'll get a merge conflict that looks something like this:
+-
+-[source,console]
+-----
+-$ git merge iss53
+-Auto-merging index.html
+-CONFLICT (content): Merge conflict in index.html
+-Automatic merge failed; fix conflicts and then commit the result.
+-----
++If you changed the same part of the same file differently in the two branches you're merging together, Git won't be able to merge them cleanly.
++If your fix for issue #53 modified the same part of a file as the `hotfix`, you'll get a merge conflict that looks something like this:
+ 
+ Git hasn't automatically created a new merge commit.
+ It has paused the process while you resolve the conflict.
+ If you want to see which files are unmerged at any point after a merge conflict, you can run `git status`:
+ 
+-[source,console]
+-----
+-$ git status
+-On branch master
+-You have unmerged paths.
+-  (fix conflicts and run "git commit")
+-
+-Unmerged paths:
+-  (use "git add <file>..." to mark resolution)
+-
+-    both modified:      index.html
+-
+-no changes added to commit (use "git add" and/or "git commit -a")
+-----
+-
+ Anything that has merge conflicts and hasn't been resolved is listed as unmerged.
+ Git adds standard conflict-resolution markers to the files that have conflicts, so you can open them manually and resolve those conflicts.
+ Your file contains a section that looks something like this:
+ 
+-[source,html]
+-----
+-<<<<<<< HEAD:index.html
+-<div id="footer">contact : [e-mail]</div>
+-=======
+-<div id="footer">
+- please contact us at [e-mail]
+-</div>
+->>>>>>> iss53:index.html
+-----
+-
+ This means the version in `HEAD` (your `master` branch, because that was what you had checked out when you ran your merge command) is the top part of that block (everything above the `=======`), while the version in your `iss53` branch looks like everything in the bottom part.
+ In order to resolve the conflict, you have to either choose one side or the other or merge the contents yourself.
+ For instance, you might resolve this conflict by replacing the entire block with this:
+ 
+-[source,html]
+-----
+-<div id="footer">
+-please contact us at [e-mail]
+-</div>
+-----
+-
+-This resolution has a little of each section, and the `<<<<<<<`, `=======`, and `>>>>>>>` lines have been completely removed.
++This resolution has a little of each section, and the `>>>>>` lines have been completely removed.
+ After you've resolved each of these sections in each conflicted file, run `git add` on each file to mark it as resolved.
+ Staging the file marks it as resolved in Git.
+ 
+ If you want to use a graphical tool to resolve these issues, you can run `git mergetool`, which fires up an appropriate visual merge tool and walks you through the conflicts:(((git commands, mergetool)))
+ 
+-[source,console]
+-----
+-$ git mergetool
+-
+-This message is displayed because 'merge.tool' is not configured.
+-See 'git mergetool --tool-help' or 'git help config' for more details.
+-'git mergetool' will now attempt to use one of the following tools:
+-opendiff kdiff3 tkdiff xxdiff meld tortoisemerge gvimdiff diffuse diffmerge ecmerge p4merge araxis bc3 codecompare vimdiff emerge
+-Merging:
+-index.html
+-
+-Normal merge conflict for 'index.html':
+-  {local}: modified file
+-  {remote}: modified file
+-Hit return to start merge resolution tool (opendiff):
+-----
+-
+ If you want to use a merge tool other than the default (Git chose `opendiff` in this case because the command was run on a Mac), you can see all the supported tools listed at the top after ``one of the following tools.''
+ Just type the name of the tool you'd rather use.
+ 
+-[NOTE]
+ ====
+-If you need more advanced tools for resolving tricky merge conflicts, we cover more on merging in <<ch07-git-tools#_advanced_merging>>.
++If you need more advanced tools for resolving tricky merge conflicts, we cover more on merging in <<ch07-git-tools#r_advanced_merging>>.
+ ====
+ 
+ After you exit the merge tool, Git asks you if the merge was successful.
+ If you tell the script that it was, it stages the file to mark it as resolved for you.
+ You can run `git status` again to verify that all conflicts have been resolved:
+ 
+-[source,console]
+-----
+-$ git status
+-On branch master
+-All conflicts fixed but you are still merging.
+-  (use "git commit" to conclude merge)
+-
+-Changes to be committed:
+-
+-    modified:   index.html
+-----
+-
+ If you're happy with that, and you verify that everything that had conflicts has been staged, you can type `git commit` to finalize the merge commit.
+ The commit message by default looks something like this:
+ 
+-[source,console]
+-----
+-Merge branch 'iss53'
+-
+-Conflicts:
+-    index.html
+-#
+-# It looks like you may be committing a merge.
+-# If this is not correct, please remove the file
+-#	.git/MERGE_HEAD
+-# and try again.
+-
+-
+-# Please enter the commit message for your changes. Lines starting
+-# with '#' will be ignored, and an empty message aborts the commit.
+-# On branch master
+-# All conflicts fixed but you are still merging.
+-#
+-# Changes to be committed:
+-#	modified:   index.html
+-#
+-----
+-
+-If you think it would be helpful to others looking at this merge in the future, you can modify this commit message with details about how you resolved the merge and explain why you did the changes you made if these are not obvious.
++You can modify that message with details about how you resolved the merge if you think it would be helpful to others looking at this merge in the future – why you did what you did, if it's not obvious.
+diff -au ../../git/progit2/progit2/book/03-git-branching/sections/branch-management.asc /tmp/book/03-git-branching/sections/branch-management.asc.tmp
+--- ../../git/progit2/progit2/book/03-git-branching/sections/branch-management.asc	2020-09-12 09:27:13.221663700 +0900
++++ /tmp/book/03-git-branching/sections/branch-management.asc.tmp	2020-10-25 09:24:25.660966904 +0900
+@@ -1,4 +1,4 @@
+-[[_branch_management]]
++[[r_branch_management]]
+ === Branch Management
+ 
+ (((branches, managing)))
+@@ -22,9 +22,9 @@
+ [source,console]
+ ----
+ $ git branch -v
+-  iss53   93b412c Fix javascript issue
++  iss53   93b412c fix javascript issue
+ * master  7a98805 Merge branch 'iss53'
+-  testing 782fd34 Add scott to the author list in the readme
++  testing 782fd34 add scott to the author list in the readmes
+ ----
+ 
+ The useful `--merged` and `--no-merged` options can filter this list to branches that you have or have not yet merged into the branch you're currently on.
+@@ -59,126 +59,3 @@
+ ----
+ 
+ If you really do want to delete the branch and lose that work, you can force it with `-D`, as the helpful message points out.
+-
+-[TIP]
+-====
+-The options described above, `--merged` and `--no-merged` will, if not given a commit or branch name as an argument, show you what is, respectively, merged or not merged into your _current_ branch.
+-
+-You can always provide an additional argument to ask about the merge state with respect to some other branch without checking  that other branch out first, as in, what is not merged into the `master` branch?
+-[source,console]
+-----
+-$ git checkout testing
+-$ git branch --no-merged master
+-  topicA
+-  featureB
+-----
+-====
+-
+-==== Changing a branch name
+-
+-[CAUTION]
+-====
+-Do not rename branches that are still in use by other collaborators.
+-Do not rename a branch like master/main/mainline without having read the section "Changing the master branch name".
+-====
+-
+-Suppose you have a branch that is called _bad-branch-name_ and you want to change it to _corrected-branch-name_, while keeping all history.
+-You also want to change the branch name on the remote (GitHub, GitLab, other server).
+-How do you do this?
+-
+-Rename the branch locally with the `git branch --move` command:
+-
+-[source, console]
+-----
+-$ git branch --move bad-branch-name corrected-branch-name
+-----
+-
+-This replaces your bad-branch-name with corrected-branch-name, but this change is only local for now.
+-To let others see the corrected branch on the remote, push it:
+-
+-[source,console]
+-----
+-$ git push --set-upstream origin corrected-branch-name
+-----
+-
+-Now we'll take a brief look at where we are now:
+-
+-[source, console]
+-----
+-$ git branch --all
+-* corrected-branch-name
+-  main
+-  remotes/origin/bad-branch-name
+-  remotes/origin/corrected-branch-name
+-  remotes/origin/main
+-----
+-
+-Notice that you're on the branch corrected-branch-name.
+-The corrected branch is available on the remote.
+-However the bad branch is also still present on the remote.
+-You can delete the bad branch from the remote:
+-
+-[source,console]
+-----
+-$ git push origin --delete bad-branch-name
+-----
+-
+-Now the bad branch name is fully replaced with the corrected branch name.
+-
+-===== Changing the master branch name
+-
+-[WARNING]
+-====
+-Changing the name of a branch like master/main/mainline/default will break the integrations, services, helper utilities and build/release scripts that your repository uses.
+-Before you do this, make sure you consult with your collaborators.
+-Also make sure you do a thorough search through your repo and update any references to the old branch name in your code or scripts.
+-====
+-
+-Rename your local _master_ branch into _main_ with the following command
+-
+-[source,console]
+-----
+-$ git branch --move master main
+-----
+-
+-There's no _master_ branch locally anymore, because it's renamed to the _main_ branch.
+-
+-To let others see the new _main_ branch, you need to push it to the remote.
+-This makes the renamed branch available on the remote.
+-
+-[source,console]
+-----
+-$ git push --set-upstream origin main
+-----
+-
+-Now we end up with the following state:
+-
+-[source,console]
+-----
+-git branch --all
+-* main
+-  remotes/origin/HEAD -> origin/master
+-  remotes/origin/main
+-  remotes/origin/master
+-----
+-
+-Your local _master_ branch is gone, as it's replaced with the _main_ branch.
+-The _main_ branch is also available on the remote.
+-But the remote still has a _master_ branch.
+-Other collaborators will continue to use the _master_ branch as the base of their work, until you make some further changes.
+-
+-Now you have a few more tasks in front of you to complete the transition:
+-
+-* Any projects that depend on this one will need to update their code and/or configuration.
+-* Update any test-runner configuration files.
+-* Adjust build and release scripts.
+-* Redirect settings on your repo host for things like the repo's default branch, merge rules, and other things that match branch names.
+-* Update references to the old branch in documentation.
+-* Close or merge any pull requests that target the old branch.
+-
+-After you've done all these tasks, and are certain the main branch performs just as the _master_ branch, you can delete the _master_ branch:
+-
+-[source, console]
+-----
+-$ git push origin --delete master
+-----
+diff -au ../../git/progit2/progit2/book/03-git-branching/sections/nutshell.asc /tmp/book/03-git-branching/sections/nutshell.asc.tmp
+--- ../../git/progit2/progit2/book/03-git-branching/sections/nutshell.asc	2020-09-26 08:56:07.950296410 +0900
++++ /tmp/book/03-git-branching/sections/nutshell.asc.tmp	2020-10-25 09:24:25.667967234 +0900
+@@ -1,41 +1,34 @@
+-[[_git_branches_overview]]
++[[r_git_branches_overview]]
+ === Branches in a Nutshell
+ 
+ To really understand the way Git does branching, we need to take a step back and examine how Git stores its data.
+ 
+-As you may remember from <<ch01-getting-started#what_is_git_section>>, Git doesn't store data as a series of changesets or differences, but instead as a series of _snapshots_.
++As you may remember from <<ch01-introduction#ch01-introduction>>, Git doesn't store data as a series of changesets or differences, but instead as a series of snapshots.
+ 
+ When you make a commit, Git stores a commit object that contains a pointer to the snapshot of the content you staged.
+-This object also contains the author's name and email address, the message that you typed, and pointers to the commit or commits that directly came before this commit (its parent or parents): zero parents for the initial commit, one parent for a normal commit, and multiple parents for a commit that results from a merge of two or more branches.
++This object also contains the author's name and email, the message that you typed, and pointers to the commit or commits that directly came before this commit (its parent or parents): zero parents for the initial commit, one parent for a normal commit, and multiple parents for a commit that results from a merge of two or more branches.
+ 
+ To visualize this, let's assume that you have a directory containing three files, and you stage them all and commit.
+-Staging the files computes a checksum for each one (the SHA-1 hash we mentioned in <<ch01-getting-started#what_is_git_section>>), stores that version of the file in the Git repository (Git refers to them as _blobs_), and adds that checksum to the staging area:
++Staging the files checksums each one (the SHA-1 hash we mentioned in <<ch01-introduction#ch01-introduction>>), stores that version of the file in the Git repository (Git refers to them as blobs), and adds that checksum to the staging area:
+ 
+-[source,console]
+-----
+-$ git add README test.rb LICENSE
+-$ git commit -m 'Initial commit'
+-----
+-
+-When you create the commit by running `git commit`, Git checksums each subdirectory (in this case, just the root project directory) and stores them as a tree object in the Git repository.
++When you create the commit by running `git commit`, Git checksums each subdirectory (in this case, just the root project directory) and stores those tree objects in the Git repository.
+ Git then creates a commit object that has the metadata and a pointer to the root project tree so it can re-create that snapshot when needed.(((git commands, commit)))
+ 
+-Your Git repository now contains five objects: three _blobs_ (each representing the contents of one of the three files), one _tree_ that lists the contents of the directory and specifies which file names are stored as which blobs, and one _commit_ with the pointer to that root tree and all the commit metadata.
++Your Git repository now contains five objects: one blob for the contents of each of your three files, one tree that lists the contents of the directory and specifies which file names are stored as which blobs, and one commit with the pointer to that root tree and all the commit metadata.
+ 
+ .A commit and its tree
+-image::images/commit-and-tree.png[A commit and its tree]
++image::images/commit-and-tree.png[A commit and its tree.]
+ 
+ If you make some changes and commit again, the next commit stores a pointer to the commit that came immediately before it.
+ 
+ .Commits and their parents
+-image::images/commits-and-parents.png[Commits and their parents]
++image::images/commits-and-parents.png[Commits and their parents.]
+ 
+ A branch in Git is simply a lightweight movable pointer to one of these commits.
+ The default branch name in Git is `master`.
+ As you start making commits, you're given a `master` branch that points to the last commit you made.
+-Every time you commit, the `master` branch pointer moves forward automatically.
++Every time you commit, it moves forward automatically.
+ 
+-[NOTE]
+ ====
+ The ``master'' branch in Git is not a special branch.(((master)))
+ It is exactly like any other branch.
+@@ -43,108 +36,62 @@
+ ====
+ 
+ .A branch and its commit history
+-image::images/branch-and-history.png[A branch and its commit history]
++image::images/branch-and-history.png[A branch and its commit history.]
+ 
+-[[_create_new_branch]]
+ ==== Creating a New Branch
+ 
+-(((branches, creating)))
+-What happens when you create a new branch?
++What happens if you create a new branch?
+ Well, doing so creates a new pointer for you to move around.
+-Let's say you want to create a new branch called `testing`.
++Let's say you create a new branch called testing.
+ You do this with the `git branch` command:(((git commands, branch)))
+ 
+-[source,console]
+-----
+-$ git branch testing
+-----
+-
+ This creates a new pointer to the same commit you're currently on.
+ 
+ .Two branches pointing into the same series of commits
+-image::images/two-branches.png[Two branches pointing into the same series of commits]
++image::images/two-branches.png[Two branches pointing into the same series of commits.]
+ 
+ How does Git know what branch you're currently on?
+ It keeps a special pointer called `HEAD`.
+ Note that this is a lot different than the concept of `HEAD` in other VCSs you may be used to, such as Subversion or CVS.
+ In Git, this is a pointer to the local branch you're currently on.
+ In this case, you're still on `master`.
+-The `git branch` command only _created_ a new branch -- it didn't switch to that branch.
++The `git branch` command only _created_ a new branch – it didn't switch to that branch.
+ 
+ .HEAD pointing to a branch
+-image::images/head-to-master.png[HEAD pointing to a branch]
++image::images/head-to-master.png[HEAD pointing to a branch.]
+ 
+ You can easily see this by running a simple `git log` command that shows you where the branch pointers are pointing.
+ This option is called `--decorate`.
+ 
+-[source,console]
+-----
+-$ git log --oneline --decorate
+-f30ab (HEAD -> master, testing) Add feature #32 - ability to add new formats to the central interface
+-34ac2 Fix bug #1328 - stack overflow under certain conditions
+-98ca9 Initial commit
+-----
+-
+-You can see the `master` and `testing` branches that are right there next to the `f30ab` commit.
++You can see the ``master'' and ``testing'' branches that are right there next to the `f30ab` commit.
+ 
+-[[_switching_branches]]
+ ==== Switching Branches
+ 
+-(((branches, switching)))
+ To switch to an existing branch, you run the `git checkout` command.(((git commands, checkout)))
+ Let's switch to the new `testing` branch:
+ 
+-[source,console]
+-----
+-$ git checkout testing
+-----
+-
+ This moves `HEAD` to point to the `testing` branch.
+ 
+ .HEAD points to the current branch
+-image::images/head-to-testing.png[HEAD points to the current branch]
++image::images/head-to-testing.png[HEAD points to the current branch.]
+ 
+ What is the significance of that?
+ Well, let's do another commit:
+ 
+-[source,console]
+-----
+-$ vim test.rb
+-$ git commit -a -m 'made a change'
+-----
+-
+ .The HEAD branch moves forward when a commit is made
+-image::images/advance-testing.png[The HEAD branch moves forward when a commit is made]
++image::images/advance-testing.png[The HEAD branch moves forward when a commit is made.]
+ 
+ This is interesting, because now your `testing` branch has moved forward, but your `master` branch still points to the commit you were on when you ran `git checkout` to switch branches.
+ Let's switch back to the `master` branch:
+ 
+-[source,console]
+-----
+-$ git checkout master
+-----
+-
+-[NOTE]
+-.`git log` doesn't show _all_ the branches _all_ the time
+-====
+-If you were to run `git log` right now, you might wonder where the "testing" branch you just created went, as it would not appear in the output.
+-
+-The branch hasn't disappeared; Git just doesn't know that you're interested in that branch and it is trying to show you what it thinks you're interested in.
+-In other words, by default, `git log` will only show commit history below the branch you've checked out.
+-
+-To show commit history for the desired branch you have to explicitly specify it: `git log testing`.
+-To show all of the branches, add `--all` to your `git log` command.
+-====
+-
+ .HEAD moves when you checkout
+-image::images/checkout-master.png[HEAD moves when you checkout]
++image::images/checkout-master.png[HEAD moves when you checkout.]
+ 
+ That command did two things.
+ It moved the HEAD pointer back to point to the `master` branch, and it reverted the files in your working directory back to the snapshot that `master` points to.
+ This also means the changes you make from this point forward will diverge from an older version of the project.
+ It essentially rewinds the work you've done in your `testing` branch so you can go in a different direction.
+ 
+-[NOTE]
+ .Switching branches changes files in your working directory
+ ====
+ It's important to note that when you switch branches in Git, files in your working directory will change.
+@@ -154,36 +101,18 @@
+ 
+ Let's make a few changes and commit again:
+ 
+-[source,console]
+-----
+-$ vim test.rb
+-$ git commit -a -m 'made other changes'
+-----
+-
+-Now your project history has diverged (see <<divergent_history>>).
++Now your project history has diverged (see <<rdivergent_history>>).
+ You created and switched to a branch, did some work on it, and then switched back to your main branch and did other work.
+ Both of those changes are isolated in separate branches: you can switch back and forth between the branches and merge them together when you're ready.
+ And you did all that with simple `branch`, `checkout`, and `commit` commands.
+ 
+-[[divergent_history]]
+ .Divergent history
+-image::images/advance-master.png[Divergent history]
++image::images/advance-master.png[Divergent history.]
+ 
+ You can also see this easily with the `git log` command.
+ If you run `git log --oneline --decorate --graph --all` it will print out the history of your commits, showing where your branch pointers are and how your history has diverged.
+ 
+-[source,console]
+-----
+-$ git log --oneline --decorate --graph --all
+-* c2b9e (HEAD, master) Made other changes
+-| * 87ab2 (testing) Made a change
+-|/
+-* f30ab Add feature #32 - ability to add new formats to the central interface
+-* 34ac2 Fix bug #1328 - stack overflow under certain conditions
+-* 98ca9 initial commit of my project
+-----
+-
+-Because a branch in Git is actually a simple file that contains the 40 character SHA-1 checksum of the commit it points to, branches are cheap to create and destroy.
++Because a branch in Git is in actuality a simple file that contains the 40 character SHA-1 checksum of the commit it points to, branches are cheap to create and destroy.
+ Creating a new branch is as quick and simple as writing 41 bytes to a file (40 characters and a newline).
+ 
+ This is in sharp contrast to the way most older VCS tools branch, which involves copying all of the project's files into a second directory.
+@@ -192,18 +121,3 @@
+ These features help encourage developers to create and use branches often.
+ 
+ Let's see why you should do so.
+-
+-[NOTE]
+-.Creating a new branch and switching to it at the same time
+-====
+-It's typical to create a new branch and want to switch to that new branch at the same time -- this can be done in one operation with `git checkout -b <newbranchname>`.
+-====
+-
+-[NOTE]
+-====
+-From Git version 2.23 onwards you can use `git switch` instead of `git checkout` to:
+-
+-- Switch to an existing branch: `git switch testing-branch`.
+-- Create a new branch and switch to it: `git switch -c new-branch`. The `-c` flag stands for create, you can also use the full flag: `--create`.
+-- Return to your previously checked out branch: `git switch -`.
+-====
+diff -au ../../git/progit2/progit2/book/03-git-branching/sections/rebasing.asc /tmp/book/03-git-branching/sections/rebasing.asc.tmp
+--- ../../git/progit2/progit2/book/03-git-branching/sections/rebasing.asc	2020-08-17 16:38:51.075694960 +0900
++++ /tmp/book/03-git-branching/sections/rebasing.asc.tmp	2020-10-25 09:24:25.673967517 +0900
+@@ -1,144 +1,94 @@
+-[[_rebasing]]
++[[r_rebasing]]
+ === Rebasing
+ 
+-(((rebasing)))
+ In Git, there are two main ways to integrate changes from one branch into another: the `merge` and the `rebase`.
+ In this section you'll learn what rebasing is, how to do it, why it's a pretty amazing tool, and in what cases you won't want to use it.
+ 
+ ==== The Basic Rebase
+ 
+-If you go back to an earlier example from <<_basic_merging>>, you can see that you diverged your work and made commits on two different branches.
++If you go back to an earlier example from <<r_basic_merging>>, you can see that you diverged your work and made commits on two different branches.
+ 
+ .Simple divergent history
+-image::images/basic-rebase-1.png[Simple divergent history]
++image::images/basic-rebase-1.png[Simple divergent history.]
+ 
+ The easiest way to integrate the branches, as we've already covered, is the `merge` command.
+ It performs a three-way merge between the two latest branch snapshots (`C3` and `C4`) and the most recent common ancestor of the two (`C2`), creating a new snapshot (and commit).
+ 
+-[[rebasing-merging-example]]
+ .Merging to integrate diverged work history
+-image::images/basic-rebase-2.png[Merging to integrate diverged work history]
++image::images/basic-rebase-2.png[Merging to integrate diverged work history.]
+ 
+ However, there is another way: you can take the patch of the change that was introduced in `C4` and reapply it on top of `C3`.
+ In Git, this is called _rebasing_.
+-With the `rebase` command, you can take all the changes that were committed on one branch and replay them on a different branch.(((git commands, rebase)))
++With the `rebase` command, you can take all the changes that were committed on one branch and replay them on another one.(((git commands, rebase)))
+ 
+-For this example, you would check out the `experiment` branch, and then rebase it onto the `master` branch as follows:
++In this example, you'd run the following:
+ 
+-[source,console]
+-----
+-$ git checkout experiment
+-$ git rebase master
+-First, rewinding head to replay your work on top of it...
+-Applying: added staged command
+-----
+-
+-This operation works by going to the common ancestor of the two branches (the one you're on and the one you're rebasing onto), getting the diff introduced by each commit of the branch you're on, saving those diffs to temporary files, resetting the current branch to the same commit as the branch you are rebasing onto, and finally applying each change in turn.
++It works by going to the common ancestor of the two branches (the one you're on and the one you're rebasing onto), getting the diff introduced by each commit of the branch you're on, saving those diffs to temporary files, resetting the current branch to the same commit as the branch you are rebasing onto, and finally applying each change in turn.
+ 
+ .Rebasing the change introduced in `C4` onto `C3`
+-image::images/basic-rebase-3.png[Rebasing the change introduced in `C4` onto `C3`]
++image::images/basic-rebase-3.png[Rebasing the change introduced in `C4` onto `C3`.]
+ 
+ At this point, you can go back to the `master` branch and do a fast-forward merge.
+ 
+-[source,console]
+-----
+-$ git checkout master
+-$ git merge experiment
+-----
+-
+-.Fast-forwarding the `master` branch
+-image::images/basic-rebase-4.png[Fast-forwarding the `master` branch]
++.Fast-forwarding the master branch
++image::images/basic-rebase-4.png[Fast-forwarding the master branch.]
+ 
+-Now, the snapshot pointed to by `C4'` is exactly the same as the one that was pointed to by `C5` in <<rebasing-merging-example,the merge example>>.
++Now, the snapshot pointed to by `C4'` is exactly the same as the one that was pointed to by `C5` in the merge example.
+ There is no difference in the end product of the integration, but rebasing makes for a cleaner history.
+ If you examine the log of a rebased branch, it looks like a linear history: it appears that all the work happened in series, even when it originally happened in parallel.
+ 
+-Often, you'll do this to make sure your commits apply cleanly on a remote branch -- perhaps in a project to which you're trying to contribute but that you don't maintain.
++Often, you'll do this to make sure your commits apply cleanly on a remote branch – perhaps in a project to which you're trying to contribute but that you don't maintain.
+ In this case, you'd do your work in a branch and then rebase your work onto `origin/master` when you were ready to submit your patches to the main project.
+-That way, the maintainer doesn't have to do any integration work -- just a fast-forward or a clean apply.
++That way, the maintainer doesn't have to do any integration work – just a fast-forward or a clean apply.
+ 
+-Note that the snapshot pointed to by the final commit you end up with, whether it's the last of the rebased commits for a rebase or the final merge commit after a merge, is the same snapshot -- it's only the history that is different.
++Note that the snapshot pointed to by the final commit you end up with, whether it's the last of the rebased commits for a rebase or the final merge commit after a merge, is the same snapshot – it's only the history that is different.
+ Rebasing replays changes from one line of work onto another in the order they were introduced, whereas merging takes the endpoints and merges them together.
+ 
+ ==== More Interesting Rebases
+ 
+ You can also have your rebase replay on something other than the rebase target branch.
+-Take a history like <<rbdiag_e>>, for example.
++Take a history like <<rrbdiag_e>>, for example.
+ You branched a topic branch (`server`) to add some server-side functionality to your project, and made a commit.
+ Then, you branched off that to make the client-side changes (`client`) and committed a few times.
+ Finally, you went back to your server branch and did a few more commits.
+ 
+-[[rbdiag_e]]
+ .A history with a topic branch off another topic branch
+-image::images/interesting-rebase-1.png[A history with a topic branch off another topic branch]
++image::images/interesting-rebase-1.png[A history with a topic branch off another topic branch.]
+ 
+ Suppose you decide that you want to merge your client-side changes into your mainline for a release, but you want to hold off on the server-side changes until it's tested further.
+-You can take the changes on `client` that aren't on `server` (`C8` and `C9`) and replay them on your `master` branch by using the `--onto` option of `git rebase`:
++You can take the changes on client that aren't on server (`C8` and `C9`) and replay them on your `master` branch by using the `--onto` option of `git rebase`:
+ 
+-[source,console]
+-----
+-$ git rebase --onto master server client
+-----
+-
+-This basically says, ``Take the `client` branch, figure out the patches since it diverged from the `server` branch, and replay these patches in the `client` branch as if it was based directly off the `master` branch instead.''
++This basically says, ``Check out the client branch, figure out the patches from the common ancestor of the `client` and `server` branches, and then replay them onto `master`.''
+ It's a bit complex, but the result is pretty cool.
+ 
+ .Rebasing a topic branch off another topic branch
+-image::images/interesting-rebase-2.png[Rebasing a topic branch off another topic branch]
++image::images/interesting-rebase-2.png[Rebasing a topic branch off another topic branch.]
+ 
+-Now you can fast-forward your `master` branch (see <<rbdiag_g>>):
++Now you can fast-forward your `master` branch (see <<rrbdiag_g>>):
+ 
+-[source,console]
+-----
+-$ git checkout master
+-$ git merge client
+-----
+-
+-[[rbdiag_g]]
+-.Fast-forwarding your `master` branch to include the client branch changes
+-image::images/interesting-rebase-3.png[Fast-forwarding your `master` branch to include the client branch changes]
++.Fast-forwarding your master branch to include the client branch changes
++image::images/interesting-rebase-3.png[Fast-forwarding your master branch to include the client branch changes.]
+ 
+ Let's say you decide to pull in your server branch as well.
+-You can rebase the `server` branch onto the `master` branch without having to check it out first by running `git rebase <basebranch> <topicbranch>` -- which checks out the topic branch (in this case, `server`) for you and replays it onto the base branch (`master`):
++You can rebase the server branch onto the `master` branch without having to check it out first by running `git rebase [basebranch] [topicbranch]` – which checks out the topic branch (in this case, `server`) for you and replays it onto the base branch (`master`):
++
++This replays your `server` work on top of your `master` work, as shown in <<rrbdiag_h>>.
+ 
+-[source,console]
+-----
+-$ git rebase master server
+-----
+-
+-This replays your `server` work on top of your `master` work, as shown in <<rbdiag_h>>.
+-
+-[[rbdiag_h]]
+-.Rebasing your server branch on top of your `master` branch
+-image::images/interesting-rebase-4.png[Rebasing your server branch on top of your `master` branch]
++.Rebasing your server branch on top of your master branch
++image::images/interesting-rebase-4.png[Rebasing your server branch on top of your master branch.]
+ 
+ Then, you can fast-forward the base branch (`master`):
+ 
+-[source,console]
+-----
+-$ git checkout master
+-$ git merge server
+-----
+-
+-You can remove the `client` and `server` branches because all the work is integrated and you don't need them anymore, leaving your history for this entire process looking like <<rbdiag_i>>:
+-
+-[source,console]
+-----
+-$ git branch -d client
+-$ git branch -d server
+-----
++You can remove the `client` and `server` branches because all the work is integrated and you don't need them anymore, leaving your history for this entire process looking like <<rrbdiag_i>>:
+ 
+-[[rbdiag_i]]
+ .Final commit history
+-image::images/interesting-rebase-5.png[Final commit history]
++image::images/interesting-rebase-5.png[Final commit history.]
+ 
+-[[_rebase_peril]]
+ ==== The Perils of Rebasing
+ 
+-(((rebasing, perils of)))
+ Ahh, but the bliss of rebasing isn't without its drawbacks, which can be summed up in a single line:
+ 
+-*Do not rebase commits that exist outside your repository and that people may have based work on.*
++*Do not rebase commits that exist outside your repository.*
+ 
+ If you follow that guideline, you'll be fine.
+ If you don't, people will hate you, and you'll be scorned by friends and family.
+@@ -162,22 +112,19 @@
+ Next, the person who pushed the merged work decides to go back and rebase their work instead; they do a `git push --force` to overwrite the history on the server.
+ You then fetch from that server, bringing down the new commits.
+ 
+-[[_pre_merge_rebase_work]]
+ .Someone pushes rebased commits, abandoning commits you've based your work on
+ image::images/perils-of-rebasing-3.png["Someone pushes rebased commits, abandoning commits you've based your work on."]
+ 
+ Now you're both in a pickle.
+ If you do a `git pull`, you'll create a merge commit which includes both lines of history, and your repository will look like this:
+ 
+-[[_merge_rebase_work]]
+ .You merge in the same work again into a new merge commit
+-image::images/perils-of-rebasing-4.png[You merge in the same work again into a new merge commit]
++image::images/perils-of-rebasing-4.png[You merge in the same work again into a new merge commit.]
+ 
+ If you run a `git log` when your history looks like this, you'll see two commits that have the same author, date, and message, which will be confusing.
+ Furthermore, if you push this history back up to the server, you'll reintroduce all those rebased commits to the central server, which can further confuse people.
+ It's pretty safe to assume that the other developer doesn't want `C4` and `C6` to be in the history; that's why they rebased in the first place.
+ 
+-[[_rebase_rebase]]
+ ==== Rebase When You Rebase
+ 
+ If you *do* find yourself in a situation like this, Git has some further magic that might help you out.
+@@ -188,20 +135,19 @@
+ 
+ If you pull down work that was rewritten and rebase it on top of the new commits from your partner, Git can often successfully figure out what is uniquely yours and apply them back on top of the new branch.
+ 
+-For instance, in the previous scenario, if instead of doing a merge when we're at <<_pre_merge_rebase_work>> we run `git rebase teamone/master`, Git will:
++For instance, in the previous scenario, if instead of doing a merge when we're at <<r_pre_merge_rebase_work>> we run `git rebase teamone/master`, Git will:
+ 
+ * Determine what work is unique to our branch (C2, C3, C4, C6, C7)
+ * Determine which are not merge commits (C2, C3, C4)
+ * Determine which have not been rewritten into the target branch (just C2 and C3, since C4 is the same patch as C4')
+ * Apply those commits to the top of `teamone/master`
+ 
+-So instead of the result we see in <<_merge_rebase_work>>, we would end up with something more like <<_rebase_rebase_work>>.
++So instead of the result we see in <<r_merge_rebase_work>>, we would end up with something more like <<r_rebase_rebase_work>>.
+ 
+-[[_rebase_rebase_work]]
+-.Rebase on top of force-pushed rebase work
+-image::images/perils-of-rebasing-5.png[Rebase on top of force-pushed rebase work]
++.Rebase on top of force-pushed rebase work.
++image::images/perils-of-rebasing-5.png[Rebase on top of force-pushed rebase work.]
+ 
+-This only works if `C4` and `C4'` that your partner made are almost exactly the same patch.
++This only works if C4 and C4' that your partner made are almost exactly the same patch.
+ Otherwise the rebase won't be able to tell that it's a duplicate and will add another C4-like patch (which will probably fail to apply cleanly, since the changes would already be at least somewhat there).
+ 
+ You can also simplify this by running a `git pull --rebase` instead of a normal `git pull`.
+@@ -209,15 +155,13 @@
+ 
+ If you are using `git pull` and want to make `--rebase` the default, you can set the `pull.rebase` config value with something like `git config --global pull.rebase true`.
+ 
+-If you only ever rebase commits that have never left your own computer, you'll be just fine.
+-If you rebase commits that have been pushed, but that no one else has based commits from, you'll also be fine.
++If you treat rebasing as a way to clean up and work with commits before you push them, and if you only rebase commits that have never been available publicly, then you'll be fine.
+ If you rebase commits that have already been pushed publicly, and people may have based work on those commits, then you may be in for some frustrating trouble, and the scorn of your teammates.
+ 
+ If you or a partner does find it necessary at some point, make sure everyone knows to run `git pull --rebase` to try to make the pain after it happens a little bit simpler.
+ 
+ ==== Rebase vs. Merge
+ 
+-(((rebasing, vs. merging)))(((merging, vs. rebasing)))
+ Now that you've seen rebasing and merging in action, you may be wondering which one is better.
+ Before we can answer this, let's step back a bit and talk about what history means.
+ 
+@@ -228,13 +172,11 @@
+ That's how it happened, and the repository should preserve that for posterity.
+ 
+ The opposing point of view is that the commit history is the *story of how your project was made.*
+-You wouldn't publish the first draft of a book, so why show your messy work?
+-When you're working on a project, you may need a record of all your missteps and dead-end paths, but when it's time to show your work to the world, you may want to tell a more coherent story of how to get from A to B.
+-People in this camp use tools like rebase and filter-branch to rewrite their commits before they're merged into the mainline branch.
+-They use tools like `rebase` and `filter-branch`, to tell the story in the way that's best for future readers.
++You wouldn't publish the first draft of a book, and the manual for how to maintain your software deserves careful editing.
++This is the camp that uses tools like rebase and filter-branch to tell the story in the way that's best for future readers.
+ 
+ Now, to the question of whether merging or rebasing is better: hopefully you'll see that it's not that simple.
+ Git is a powerful tool, and allows you to do many things to and with your history, but every team and every project is different.
+ Now that you know how both of these things work, it's up to you to decide which one is best for your particular situation.
+ 
+-You can get the best of both worlds: rebase local changes before pushing to clean up your work, but never rebase anything that you've pushed somewhere.
++In general the way to get the best of both worlds is to rebase local changes you've made but haven't shared yet before you push them in order to clean up your story, but never rebase anything you've pushed somewhere.
+diff -au ../../git/progit2/progit2/book/03-git-branching/sections/remote-branches.asc /tmp/book/03-git-branching/sections/remote-branches.asc.tmp
+--- ../../git/progit2/progit2/book/03-git-branching/sections/remote-branches.asc	2020-07-04 16:36:46.723685453 +0900
++++ /tmp/book/03-git-branching/sections/remote-branches.asc.tmp	2020-10-25 09:24:25.680967847 +0900
+@@ -1,25 +1,23 @@
+-[[_remote_branches]]
++[[r_remote_branches]]
+ === Remote Branches
+ 
+-(((branches, remote)))(((references, remote)))
+ Remote references are references (pointers) in your remote repositories, including branches, tags, and so on.
+-You can get a full list of remote references explicitly with `git ls-remote <remote>`, or `git remote show <remote>` for remote branches as well as more information.
++You can get a full list of remote references explicitly with `git ls-remote [remote]`, or `git remote show [remote]` for remote branches as well as more information.
+ Nevertheless, a more common way is to take advantage of remote-tracking branches.
+ 
+ Remote-tracking branches are references to the state of remote branches.
+-They're local references that you can't move; Git moves them for you whenever you do any network communication, to make sure they accurately represent the state of the remote repository.
+-Think of them as bookmarks, to remind you where the branches in your remote repositories were the last time you connected to them.
++They're local references that you can't move; they're moved automatically for you whenever you do any network communication.
++Remote-tracking branches act as bookmarks to remind you where the branches in your remote repositories were the last time you connected to them.
+ 
+-Remote-tracking branch names take the form `<remote>/<branch>`.
++They take the form `(remote)/(branch)`.
+ For instance, if you wanted to see what the `master` branch on your `origin` remote looked like as of the last time you communicated with it, you would check the `origin/master` branch.
+-If you were working on an issue with a partner and they pushed up an `iss53` branch, you might have your own local `iss53` branch, but the branch on the server would be represented by the remote-tracking branch `origin/iss53`.
++If you were working on an issue with a partner and they pushed up an `iss53` branch, you might have your own local `iss53` branch; but the branch on the server would point to the commit at `origin/iss53`.
+ 
+ This may be a bit confusing, so let's look at an example.
+ Let's say you have a Git server on your network at `git.ourcompany.com`.
+ If you clone from this, Git's `clone` command automatically names it `origin` for you, pulls down all its data, creates a pointer to where its `master` branch is, and names it `origin/master` locally.
+ Git also gives you your own local `master` branch starting at the same place as origin's `master` branch, so you have something to work from.
+ 
+-[NOTE]
+ .``origin'' is not special
+ ====
+ Just like the branch name ``master'' does not have any special meaning in Git, neither does ``origin''.
+@@ -31,62 +29,47 @@
+ image::images/remote-branches-1.png[Server and local repositories after cloning.]
+ 
+ If you do some work on your local `master` branch, and, in the meantime, someone else pushes to `git.ourcompany.com` and updates its `master` branch, then your histories move forward differently.
+-Also, as long as you stay out of contact with your `origin` server, your `origin/master` pointer doesn't move.
++Also, as long as you stay out of contact with your origin server, your `origin/master` pointer doesn't move.
+ 
+ .Local and remote work can diverge
+-image::images/remote-branches-2.png[Local and remote work can diverge]
++image::images/remote-branches-2.png[Local and remote work can diverge.]
+ 
+-To synchronize your work with a given remote, you run a `git fetch <remote>` command (in our case, `git fetch origin`).
++To synchronize your work, you run a `git fetch origin` command.
+ This command looks up which server ``origin'' is (in this case, it's `git.ourcompany.com`), fetches any data from it that you don't yet have, and updates your local database, moving your `origin/master` pointer to its new, more up-to-date position.
+ 
+-.`git fetch` updates your remote-tracking branches
+-image::images/remote-branches-3.png[`git fetch` updates your remote references]
++.`git fetch` updates your remote references
++image::images/remote-branches-3.png[`git fetch` updates your remote references.]
+ 
+ To demonstrate having multiple remote servers and what remote branches for those remote projects look like, let's assume you have another internal Git server that is used only for development by one of your sprint teams.
+ This server is at `git.team1.ourcompany.com`.
+-You can add it as a new remote reference to the project you're currently working on by running the `git remote add` command as we covered in <<ch02-git-basics-chapter#ch02-git-basics-chapter>>.
++You can add it as a new remote reference to the project you're currently working on by running the `git remote add` command as we covered in <<ch02-git-basics#ch02-git-basics>>.
+ Name this remote `teamone`, which will be your shortname for that whole URL.
+ 
+ .Adding another server as a remote
+-image::images/remote-branches-4.png[Adding another server as a remote]
++image::images/remote-branches-4.png[Adding another server as a remote.]
+ 
+ Now, you can run `git fetch teamone` to fetch everything the remote `teamone` server has that you don't have yet.
+ Because that server has a subset of the data your `origin` server has right now, Git fetches no data but sets a remote-tracking branch called `teamone/master` to point to the commit that `teamone` has as its `master` branch.
+ 
+-.Remote-tracking branch for `teamone/master`
+-image::images/remote-branches-5.png[Remote tracking branch for `teamone/master`]
++.Remote tracking branch for `teamone/master`
++image::images/remote-branches-5.png[Remote tracking branch for `teamone/master`.]
+ 
+-[[_pushing_branches]]
+ ==== Pushing
+ 
+-(((pushing)))
+-When you want to share a branch with the world, you need to push it up to a remote to which you have write access.
+-Your local branches aren't automatically synchronized to the remotes you write to -- you have to explicitly push the branches you want to share.
++When you want to share a branch with the world, you need to push it up to a remote that you have write access to.
++Your local branches aren't automatically synchronized to the remotes you write to – you have to explicitly push the branches you want to share.
+ That way, you can use private branches for work you don't want to share, and push up only the topic branches you want to collaborate on.
+ 
+ If you have a branch named `serverfix` that you want to work on with others, you can push it up the same way you pushed your first branch.
+ Run `git push <remote> <branch>`:(((git commands, push)))
+ 
+-[source,console]
+-----
+-$ git push origin serverfix
+-Counting objects: 24, done.
+-Delta compression using up to 8 threads.
+-Compressing objects: 100% (15/15), done.
+-Writing objects: 100% (24/24), 1.91 KiB | 0 bytes/s, done.
+-Total 24 (delta 2), reused 0 (delta 0)
+-To https://github.com/schacon/simplegit
+- * [new branch]      serverfix -> serverfix
+-----
+-
+ This is a bit of a shortcut.
+-Git automatically expands the `serverfix` branchname out to `refs/heads/serverfix:refs/heads/serverfix`, which means, ``Take my `serverfix` local branch and push it to update the remote's `serverfix` branch.''
++Git automatically expands the `serverfix` branchname out to `refs/heads/serverfix:refs/heads/serverfix`, which means, ``Take my serverfix local branch and push it to update the remote's serverfix branch.''
+ We'll go over the `refs/heads/` part in detail in <<ch10-git-internals#ch10-git-internals>>, but you can generally leave it off.
+-You can also do `git push origin serverfix:serverfix`, which does the same thing -- it says, ``Take my serverfix and make it the remote's serverfix.''
++You can also do `git push origin serverfix:serverfix`, which does the same thing – it says, ``Take my serverfix and make it the remote's serverfix.''
+ You can use this format to push a local branch into a remote branch that is named differently.
+ If you didn't want it to be called `serverfix` on the remote, you could instead run `git push origin serverfix:awesomebranch` to push your local `serverfix` branch to the `awesomebranch` branch on the remote project.
+ 
+-[NOTE]
+ .Don't type your password every time
+ ====
+ If you're using an HTTPS URL to push over, the Git server will ask you for your username and password for authentication.
+@@ -95,87 +78,38 @@
+ If you don't want to type it every single time you push, you can set up a ``credential cache''.
+ The simplest is just to keep it in memory for a few minutes, which you can easily set up by running `git config --global credential.helper cache`.
+ 
+-For more information on the various credential caching options available, see <<ch07-git-tools#_credential_caching>>.
++For more information on the various credential caching options available, see <<ch07-git-tools#r_credential_caching>>.
+ ====
+ 
+ The next time one of your collaborators fetches from the server, they will get a reference to where the server's version of `serverfix` is under the remote branch `origin/serverfix`:
+ 
+-[source,console]
+-----
+-$ git fetch origin
+-remote: Counting objects: 7, done.
+-remote: Compressing objects: 100% (2/2), done.
+-remote: Total 3 (delta 0), reused 3 (delta 0)
+-Unpacking objects: 100% (3/3), done.
+-From https://github.com/schacon/simplegit
+- * [new branch]      serverfix    -> origin/serverfix
+-----
+-
+ It's important to note that when you do a fetch that brings down new remote-tracking branches, you don't automatically have local, editable copies of them.
+-In other words, in this case, you don't have a new `serverfix` branch -- you have only an `origin/serverfix` pointer that you can't modify.
++In other words, in this case, you don't have a new `serverfix` branch – you only have an `origin/serverfix` pointer that you can't modify.
+ 
+ To merge this work into your current working branch, you can run `git merge origin/serverfix`.
+ If you want your own `serverfix` branch that you can work on, you can base it off your remote-tracking branch:
+ 
+-[source,console]
+-----
+-$ git checkout -b serverfix origin/serverfix
+-Branch serverfix set up to track remote branch serverfix from origin.
+-Switched to a new branch 'serverfix'
+-----
+-
+ This gives you a local branch that you can work on that starts where `origin/serverfix` is.
+ 
+-[[_tracking_branches]]
+ ==== Tracking Branches
+ 
+-(((branches, tracking)))(((branches, upstream)))
+ Checking out a local branch from a remote-tracking branch automatically creates what is called a ``tracking branch'' (and the branch it tracks is called an ``upstream branch'').
+ Tracking branches are local branches that have a direct relationship to a remote branch.
+-If you're on a tracking branch and type `git pull`, Git automatically knows which server to fetch from and which branch to merge in.
++If you're on a tracking branch and type `git pull`, Git automatically knows which server to fetch from and branch to merge into.
+ 
+ When you clone a repository, it generally automatically creates a `master` branch that tracks `origin/master`.
+-However, you can set up other tracking branches if you wish -- ones that track branches on other remotes, or don't track the `master` branch.
+-The simple case is the example you just saw, running `git checkout -b <branch> <remote>/<branch>`.
+-This is a common enough operation that Git provides the `--track` shorthand:
+-
+-[source,console]
+-----
+-$ git checkout --track origin/serverfix
+-Branch serverfix set up to track remote branch serverfix from origin.
+-Switched to a new branch 'serverfix'
+-----
+-
+-In fact, this is so common that there's even a shortcut for that shortcut.
+-If the branch name you're trying to checkout (a) doesn't exist and (b) exactly matches a name on only one remote, Git will create a tracking branch for you:
+-
+-[source,console]
+-----
+-$ git checkout serverfix
+-Branch serverfix set up to track remote branch serverfix from origin.
+-Switched to a new branch 'serverfix'
+-----
++However, you can set up other tracking branches if you wish – ones that track branches on other remotes, or don't track the `master` branch.
++The simple case is the example you just saw, running `git checkout -b [branch] [remotename]/[branch]`.
++This is a common enough operation that git provides the `--track` shorthand:
+ 
+-To set up a local branch with a different name than the remote branch, you can easily use the first version with a different local branch name:
++In fact, this is so common that there's even a shortcut for that shortcut. If the branch name you're trying to checkout (a) doesn't exist and (b) exactly matches a name on only one remote, Git will create a tracking branch for you:
+ 
+-[source,console]
+-----
+-$ git checkout -b sf origin/serverfix
+-Branch sf set up to track remote branch serverfix from origin.
+-Switched to a new branch 'sf'
+-----
++To set up a local branch with a different name than the remote branch, you can easily use the first version with a different local branch name:
+ 
+ Now, your local branch `sf` will automatically pull from `origin/serverfix`.
+ 
+ If you already have a local branch and want to set it to a remote branch you just pulled down, or want to change the upstream branch you're tracking, you can use the `-u` or `--set-upstream-to` option to `git branch` to explicitly set it at any time.
+ 
+-[source,console]
+-----
+-$ git branch -u origin/serverfix
+-Branch serverfix set up to track remote branch serverfix from origin.
+-----
+-
+-[NOTE]
+ .Upstream shorthand
+ ====
+ When you have a tracking branch set up, you can reference its upstream branch with the `@{upstream}` or `@{u}` shorthand.
+@@ -185,15 +119,6 @@
+ If you want to see what tracking branches you have set up, you can use the `-vv` option to `git branch`.
+ This will list out your local branches with more information including what each branch is tracking and if your local branch is ahead, behind or both.
+ 
+-[source,console]
+-----
+-$ git branch -vv
+-  iss53     7e424c3 [origin/iss53: ahead 2] Add forgotten brackets
+-  master    1ae2a45 [origin/master] Deploy index fix
+-* serverfix f8674d9 [teamone/server-fix-good: ahead 3, behind 1] This should do it
+-  testing   5ea463a Try something new
+-----
+-
+ So here we can see that our `iss53` branch is tracking `origin/iss53` and is ``ahead'' by two, meaning that we have two commits locally that are not pushed to the server.
+ We can also see that our `master` branch is tracking `origin/master` and is up to date.
+ Next we can see that our `serverfix` branch is tracking the `server-fix-good` branch on our `teamone` server and is ahead by three and behind by one, meaning that there is one commit on the server we haven't merged in yet and three commits locally that we haven't pushed.
+@@ -202,37 +127,22 @@
+ It's important to note that these numbers are only since the last time you fetched from each server.
+ This command does not reach out to the servers, it's telling you about what it has cached from these servers locally.
+ If you want totally up to date ahead and behind numbers, you'll need to fetch from all your remotes right before running this.
+-You could do that like this:
+-
+-[source,console]
+-----
+-$ git fetch --all; git branch -vv
+-----
++You could do that like this: `git fetch --all; git branch -vv`
+ 
+ ==== Pulling
+ 
+-(((pulling)))
+-While the `git fetch` command will fetch all the changes on the server that you don't have yet, it will not modify your working directory at all.
++While the `git fetch` command will fetch down all the changes on the server that you don't have yet, it will not modify your working directory at all.
+ It will simply get the data for you and let you merge it yourself.
+ However, there is a command called `git pull` which is essentially a `git fetch` immediately followed by a `git merge` in most cases.
+ If you have a tracking branch set up as demonstrated in the last section, either by explicitly setting it or by having it created for you by the `clone` or `checkout` commands, `git pull` will look up what server and branch your current branch is tracking, fetch from that server and then try to merge in that remote branch.
+ 
+ Generally it's better to simply use the `fetch` and `merge` commands explicitly as the magic of `git pull` can often be confusing.
+ 
+-[[_delete_branches]]
+ ==== Deleting Remote Branches
+ 
+-(((branches, deleting remote)))
+-Suppose you're done with a remote branch -- say you and your collaborators are finished with a feature and have merged it into your remote's `master` branch (or whatever branch your stable codeline is in).
++Suppose you're done with a remote branch – say you and your collaborators are finished with a feature and have merged it into your remote's `master` branch (or whatever branch your stable codeline is in).
+ You can delete a remote branch using the `--delete` option to `git push`.
+ If you want to delete your `serverfix` branch from the server, you run the following:
+ 
+-[source,console]
+-----
+-$ git push origin --delete serverfix
+-To https://github.com/schacon/simplegit
+- - [deleted]         serverfix
+-----
+-
+ Basically all this does is remove the pointer from the server.
+ The Git server will generally keep the data there for a while until a garbage collection runs, so if it was accidentally deleted, it's often easy to recover.
+diff -au ../../git/progit2/progit2/book/03-git-branching/sections/workflows.asc /tmp/book/03-git-branching/sections/workflows.asc.tmp
+--- ../../git/progit2/progit2/book/03-git-branching/sections/workflows.asc	2020-07-04 16:36:46.723685453 +0900
++++ /tmp/book/03-git-branching/sections/workflows.asc.tmp	2020-10-25 09:24:25.686968130 +0900
+@@ -1,39 +1,35 @@
+ === Branching Workflows
+ 
+ Now that you have the basics of branching and merging down, what can or should you do with them?
+-In this section, we'll cover some common workflows that this lightweight branching makes possible, so you can decide if you would like to incorporate them into your own development cycle.
++In this section, we'll cover some common workflows that this lightweight branching makes possible, so you can decide if you would like to incorporate it into your own development cycle.
+ 
+ ==== Long-Running Branches
+ 
+-(((branches, long-running)))
+ Because Git uses a simple three-way merge, merging from one branch into another multiple times over a long period is generally easy to do.
+ This means you can have several branches that are always open and that you use for different stages of your development cycle; you can merge regularly from some of them into others.
+ 
+-Many Git developers have a workflow that embraces this approach, such as having only code that is entirely stable in their `master` branch -- possibly only code that has been or will be released.
+-They have another parallel branch named `develop` or `next` that they work from or use to test stability -- it isn't necessarily always stable, but whenever it gets to a stable state, it can be merged into `master`.
++Many Git developers have a workflow that embraces this approach, such as having only code that is entirely stable in their `master` branch – possibly only code that has been or will be released.
++They have another parallel branch named `develop` or `next` that they work from or use to test stability – it isn't necessarily always stable, but whenever it gets to a stable state, it can be merged into `master`.
+ It's used to pull in topic branches (short-lived branches, like your earlier `iss53` branch) when they're ready, to make sure they pass all the tests and don't introduce bugs.
+ 
+ In reality, we're talking about pointers moving up the line of commits you're making.
+ The stable branches are farther down the line in your commit history, and the bleeding-edge branches are farther up the history.
+ 
+ .A linear view of progressive-stability branching
+-image::images/lr-branches-1.png[A linear view of progressive-stability branching]
++image::images/lr-branches-1.png[A linear view of progressive-stability branching.]
+ 
+ It's generally easier to think about them as work silos, where sets of commits graduate to a more stable silo when they're fully tested.
+ 
+-[[lrbranch_b]]
+ .A ``silo'' view of progressive-stability branching
+-image::images/lr-branches-2.png[A ``silo'' view of progressive-stability branching]
++image::images/lr-branches-2.png[A ``silo'' view of progressive-stability branching.]
+ 
+ You can keep doing this for several levels of stability.
+ Some larger projects also have a `proposed` or `pu` (proposed updates) branch that has integrated branches that may not be ready to go into the `next` or `master` branch.
+ The idea is that your branches are at various levels of stability; when they reach a more stable level, they're merged into the branch above them.
+ Again, having multiple long-running branches isn't necessary, but it's often helpful, especially when you're dealing with very large or complex projects.
+ 
+-[[_topic_branch]]
+ ==== Topic Branches
+ 
+-(((branches, topic)))
+ Topic branches, however, are useful in projects of any size.
+ A topic branch is a short-lived branch that you create and use for a single particular feature or related work.
+ This is something you've likely never done with a VCS before because it's generally too expensive to create and merge branches.
+@@ -41,23 +37,23 @@
+ 
+ You saw this in the last section with the `iss53` and `hotfix` branches you created.
+ You did a few commits on them and deleted them directly after merging them into your main branch.
+-This technique allows you to context-switch quickly and completely -- because your work is separated into silos where all the changes in that branch have to do with that topic, it's easier to see what has happened during code review and such.
++This technique allows you to context-switch quickly and completely – because your work is separated into silos where all the changes in that branch have to do with that topic, it's easier to see what has happened during code review and such.
+ You can keep the changes there for minutes, days, or months, and merge them in when they're ready, regardless of the order in which they were created or worked on.
+ 
+ Consider an example of doing some work (on `master`), branching off for an issue (`iss91`), working on it for a bit, branching off the second branch to try another way of handling the same thing (`iss91v2`), going back to your `master` branch and working there for a while, and then branching off there to do some work that you're not sure is a good idea (`dumbidea` branch).
+ Your commit history will look something like this:
+ 
+ .Multiple topic branches
+-image::images/topic-branches-1.png[Multiple topic branches]
++image::images/topic-branches-1.png[Multiple topic branches.]
+ 
+ Now, let's say you decide you like the second solution to your issue best (`iss91v2`); and you showed the `dumbidea` branch to your coworkers, and it turns out to be genius.
+ You can throw away the original `iss91` branch (losing commits `C5` and `C6`) and merge in the other two.
+ Your history then looks like this:
+ 
+ .History after merging `dumbidea` and `iss91v2`
+-image::images/topic-branches-2.png[History after merging `dumbidea` and `iss91v2`]
++image::images/topic-branches-2.png[History after merging `dumbidea` and `iss91v2`.]
+ 
+ We will go into more detail about the various possible workflows for your Git project in <<ch05-distributed-git#ch05-distributed-git>>, so before you decide which branching scheme your next project will use, be sure to read that chapter.
+ 
+ It's important to remember when you're doing all this that these branches are completely local.
+-When you're branching and merging, everything is being done only in your Git repository -- there is no communication with the server.
++When you're branching and merging, everything is being done only in your Git repository – no server communication is happening.
+diff -au ../../git/progit2/progit2/book/04-git-server/sections/generating-ssh-key.asc /tmp/book/04-git-server/sections/generating-ssh-key.asc.tmp
+--- ../../git/progit2/progit2/book/04-git-server/sections/generating-ssh-key.asc	2020-08-05 13:56:11.288918669 +0900
++++ /tmp/book/04-git-server/sections/generating-ssh-key.asc.tmp	2020-10-25 09:24:25.690968318 +0900
+@@ -1,57 +1,21 @@
+-[[_generate_ssh_key]]
++[[r_generate_ssh_key]]
+ === Generating Your SSH Public Key
+ 
+-(((SSH keys)))
+-Many Git servers authenticate using SSH public keys.
++That being said, many Git servers authenticate using SSH public keys.
+ In order to provide a public key, each user in your system must generate one if they don't already have one.
+ This process is similar across all operating systems.
+ First, you should check to make sure you don't already have a key.
+ By default, a user's SSH keys are stored in that user's `~/.ssh` directory.
+ You can easily check to see if you have a key already by going to that directory and listing the contents:
+ 
+-[source,console]
+-----
+-$ cd ~/.ssh
+-$ ls
+-authorized_keys2  id_dsa       known_hosts
+-config            id_dsa.pub
+-----
+-
+ You're looking for a pair of files named something like `id_dsa` or `id_rsa` and a matching file with a `.pub` extension.
+-The `.pub` file is your public key, and the other file is the corresponding private key.
+-If you don't have these files (or you don't even have a `.ssh` directory), you can create them by running a program called `ssh-keygen`, which is provided with the SSH package on Linux/macOS systems and comes with Git for Windows:
+-
+-[source,console]
+-----
+-$ ssh-keygen -o
+-Generating public/private rsa key pair.
+-Enter file in which to save the key (/home/schacon/.ssh/id_rsa):
+-Created directory '/home/schacon/.ssh'.
+-Enter passphrase (empty for no passphrase):
+-Enter same passphrase again:
+-Your identification has been saved in /home/schacon/.ssh/id_rsa.
+-Your public key has been saved in /home/schacon/.ssh/id_rsa.pub.
+-The key fingerprint is:
+-d0:82:24:8e:d7:f1:bb:9b:33:53:96:93:49:da:9b:e3 [e-mail]
+-----
++The `.pub` file is your public key, and the other file is your private key.
++If you don't have these files (or you don't even have a `.ssh` directory), you can create them by running a program called `ssh-keygen`, which is provided with the SSH package on Linux/Mac systems and comes with Git for Windows:
+ 
+ First it confirms where you want to save the key (`.ssh/id_rsa`), and then it asks twice for a passphrase, which you can leave empty if you don't want to type a password when you use the key.
+-However, if you do use a password, make sure to add the `-o` option; it saves the private key in a format that is more resistant to brute-force password cracking than is the default format.
+-You can also use the `ssh-agent` tool to prevent having to enter the password each time.
+ 
+ Now, each user that does this has to send their public key to you or whoever is administrating the Git server (assuming you're using an SSH server setup that requires public keys).
+ All they have to do is copy the contents of the `.pub` file and email it.
+ The public keys look something like this:
+ 
+-[source,console]
+-----
+-$ cat ~/.ssh/id_rsa.pub
+-ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAklOUpkDHrfHY17SbrmTIpNLTGK9Tjom/BWDSU
+-GPl+nafzlHDTYW7hdI4yZ5ew18JH4JW9jbhUFrviQzM7xlELEVf4h9lFX5QVkbPppSwg0cda3
+-Pbv7kOdJ/MTyBlWXFCR+HAo3FXRitBqxiX1nKhXpHAZsMciLq8V6RjsNAQwdsdMFvSlVK/7XA
+-t3FaoJoAsncM1Q9x5+3V0Ww68/eIFmb1zuUFljQJKprrX88XypNDvjYNby6vw/Pb0rwert/En
+-mZ+AW4OZPnTPI89ZPmVMLuayrD2cE86Z/il8b+gw3r3+1nKatmIkjn2so1d01QraTlMqVSsbx
+-NrRFi9wrf+M7Q== [e-mail]
+-----
+-
+-For a more in-depth tutorial on creating an SSH key on multiple operating systems, see the GitHub guide on SSH keys at https://docs.github.com/en/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent[].
++For a more in-depth tutorial on creating an SSH key on multiple operating systems, see the GitHub guide on SSH keys at https://help.github.com/articles/generating-ssh-keys[].
+diff -au ../../git/progit2/progit2/book/04-git-server/sections/git-daemon.asc /tmp/book/04-git-server/sections/git-daemon.asc.tmp
+--- ../../git/progit2/progit2/book/04-git-server/sections/git-daemon.asc	2020-06-28 16:44:50.925015352 +0900
++++ /tmp/book/04-git-server/sections/git-daemon.asc.tmp	2020-10-25 09:24:25.694968507 +0900
+@@ -1,66 +1,33 @@
+ === Git Daemon
+ 
+-(((serving repositories, git protocol)))
+-Next we'll set up a daemon serving repositories using the ``Git'' protocol.
+-This is a common choice for fast, unauthenticated access to your Git data.
+-Remember that since this is not an authenticated service, anything you serve over this protocol is public within its network.
++Next we'll set up a daemon serving repositories over the ``Git'' protocol.
++This is common choice for fast, unauthenticated access to your Git data.
++Remember that since it's not an authenticated service, anything you serve over this protocol is public within its network.
+ 
+-If you're running this on a server outside your firewall, it should be used only for projects that are publicly visible to the world.
++If you're running this on a server outside your firewall, it should only be used for projects that are publicly visible to the world.
+ If the server you're running it on is inside your firewall, you might use it for projects that a large number of people or computers (continuous integration or build servers) have read-only access to, when you don't want to have to add an SSH key for each.
+ 
+ In any case, the Git protocol is relatively easy to set up.
+ Basically, you need to run this command in a daemonized manner:(((git commands, daemon)))
+ 
+-[source,console]
+-----
+-$ git daemon --reuseaddr --base-path=/srv/git/ /srv/git/
+-----
+-
+-The `--reuseaddr` option allows the server to restart without waiting for old connections to time out, while the `--base-path` option allows people to clone projects without specifying the entire path, and the path at the end tells the Git daemon where to look for repositories to export.
++`--reuseaddr` allows the server to restart without waiting for old connections to time out, the `--base-path` option allows people to clone projects without specifying the entire path, and the path at the end tells the Git daemon where to look for repositories to export.
+ If you're running a firewall, you'll also need to punch a hole in it at port 9418 on the box you're setting this up on.
+ 
+ You can daemonize this process a number of ways, depending on the operating system you're running.
++On an Ubuntu machine, you can use an Upstart script.
++So, in the following file
+ 
+-Since `systemd` is the most common init system among modern Linux distributions, you can use it for that purpose.
+-Simply place a file in `/etc/systemd/system/git-daemon.service` with these contents:
+-
+-[source,console]
+-----
+-[Unit]
+-Description=Start Git Daemon
+-
+-[Service]
+-ExecStart=/usr/bin/git daemon --reuseaddr --base-path=/srv/git/ /srv/git/
+-
+-Restart=always
+-RestartSec=500ms
++you put this script:
+ 
+-StandardOutput=syslog
+-StandardError=syslog
+-SyslogIdentifier=git-daemon
++For security reasons, it is strongly encouraged to have this daemon run as a user with read-only permissions to the repositories – you can easily do this by creating a new user 'git-ro' and running the daemon as them.
++For the sake of simplicity we'll simply run it as the same 'git' user that `git-shell` is running as.
+ 
+-User=git
+-Group=git
++When you restart your machine, your Git daemon will start automatically and respawn if it goes down.
++To get it running without having to reboot, you can run this:
+ 
+-[Install]
+-WantedBy=multi-user.target
+-----
+-
+-You might have noticed that Git daemon is started here with `git` as both group and user.
+-Modify it to fit your needs and make sure the provided user exists on the system.
+-Also, check that the Git binary is indeed located at `/usr/bin/git` and change the path if necessary.
+-
+-Finally, you'll run `systemctl enable git-daemon` to automatically start the service on boot, and can start and stop the service with, respectively, `systemctl start git-daemon` and `systemctl stop git-daemon`.
+-
+-On other systems, you may want to use `xinetd`, a script in your `sysvinit` system, or something else -- as long as you get that command daemonized and watched somehow.
++On other systems, you may want to use `xinetd`, a script in your `sysvinit` system, or something else – as long as you get that command daemonized and watched somehow.
+ 
+ Next, you have to tell Git which repositories to allow unauthenticated Git server-based access to.
+ You can do this in each repository by creating a file named `git-daemon-export-ok`.
+ 
+-[source,console]
+-----
+-$ cd /path/to/project.git
+-$ touch git-daemon-export-ok
+-----
+-
+ The presence of that file tells Git that it's OK to serve this project without authentication.
+diff -au ../../git/progit2/progit2/book/04-git-server/sections/git-on-a-server.asc /tmp/book/04-git-server/sections/git-on-a-server.asc.tmp
+--- ../../git/progit2/progit2/book/04-git-server/sections/git-on-a-server.asc	2020-07-04 16:36:46.723685453 +0900
++++ /tmp/book/04-git-server/sections/git-on-a-server.asc.tmp	2020-10-25 09:24:25.700968789 +0900
+@@ -1,74 +1,42 @@
+-[[_getting_git_on_a_server]]
++[[r_git_on_the_server]]
+ === Getting Git on a Server
+ 
+ Now we'll cover setting up a Git service running these protocols on your own server.
+ 
+-[NOTE]
+ ====
+-Here we'll be demonstrating the commands and steps needed to do basic, simplified installations on a Linux-based server, though it's also possible to run these services on macOS or Windows servers.
++Here we'll be demonstrating the commands and steps needed to do basic, simplified installations on a Linux based server, though it's also possible to run these services on Mac or Windows servers.
+ Actually setting up a production server within your infrastructure will certainly entail differences in security measures or operating system tools, but hopefully this will give you the general idea of what's involved.
+ ====
+ 
+-In order to initially set up any Git server, you have to export an existing repository into a new bare repository -- a repository that doesn't contain a working directory.
++In order to initially set up any Git server, you have to export an existing repository into a new bare repository – a repository that doesn't contain a working directory.
+ This is generally straightforward to do.
+ In order to clone your repository to create a new bare repository, you run the clone command with the `--bare` option.(((git commands, clone, bare)))
+-By convention, bare repository directory names end with the suffix `.git`, like so:
+-
+-[source,console]
+-----
+-$ git clone --bare my_project my_project.git
+-Cloning into bare repository 'my_project.git'...
+-done.
+-----
++By convention, bare repository directories end in `.git`, like so:
+ 
+ You should now have a copy of the Git directory data in your `my_project.git` directory.
+ 
+-This is roughly equivalent to something like:
+-
+-[source,console]
+-----
+-$ cp -Rf my_project/.git my_project.git
+-----
++This is roughly equivalent to something like
+ 
+-There are a couple of minor differences in the configuration file but, for your purpose, this is close to the same thing.
++There are a couple of minor differences in the configuration file; but for your purpose, this is close to the same thing.
+ It takes the Git repository by itself, without a working directory, and creates a directory specifically for it alone.
+ 
+-[[_bare_repo]]
+ ==== Putting the Bare Repository on a Server
+ 
+ Now that you have a bare copy of your repository, all you need to do is put it on a server and set up your protocols.
+-Let's say you've set up a server called `git.example.com` to which you have SSH access, and you want to store all your Git repositories under the `/srv/git` directory.
+-Assuming that `/srv/git` exists on that server, you can set up your new repository by copying your bare repository over:
++Let's say you've set up a server called `git.example.com` that you have SSH access to, and you want to store all your Git repositories under the `/opt/git` directory.
++Assuming that `/opt/git` exists on that server, you can set up your new repository by copying your bare repository over:
++
++At this point, other users who have SSH access to the same server which has read-access to the `/opt/git` directory can clone your repository by running
++
++If a user SSHs into a server and has write access to the `/opt/git/my_project.git` directory, they will also automatically have push access.
+ 
+-[source,console]
+-----
+-$ scp -r my_project.git [e-mail]:/srv/git
+-----
+-
+-At this point, other users who have SSH-based read access to the `/srv/git` directory on that server can clone your repository by running:
+-
+-[source,console]
+-----
+-$ git clone [e-mail]:/srv/git/my_project.git
+-----
+-
+-If a user SSHs into a server and has write access to the `/srv/git/my_project.git` directory, they will also automatically have push access.
+-
+-Git will automatically add group write permissions to a repository properly if you run the `git init` command with the `--shared` option.
+-Note that by running this command, you will not destroy any commits, refs, etc. in the process.(((git commands, init, bare)))
+-
+-[source,console]
+-----
+-$ ssh [e-mail]
+-$ cd /srv/git/my_project.git
+-$ git init --bare --shared
+-----
++Git will automatically add group write permissions to a repository properly if you run the `git init` command with the `--shared` option.(((git commands, init, bare)))
+ 
+ You see how easy it is to take a Git repository, create a bare version, and place it on a server to which you and your collaborators have SSH access.
+ Now you're ready to collaborate on the same project.
+ 
+-It's important to note that this is literally all you need to do to run a useful Git server to which several people have access -- just add SSH-able accounts on a server, and stick a bare repository somewhere that all those users have read and write access to.
+-You're ready to go -- nothing else needed.
++It's important to note that this is literally all you need to do to run a useful Git server to which several people have access – just add SSH-able accounts on a server, and stick a bare repository somewhere that all those users have read and write access to.
++You're ready to go – nothing else needed.
+ 
+ In the next few sections, you'll see how to expand to more sophisticated setups.
+ This discussion will include not having to create user accounts for each user, adding public read access to repositories, setting up web UIs and more.
+@@ -78,24 +46,23 @@
+ 
+ If you're a small outfit or are just trying out Git in your organization and have only a few developers, things can be simple for you.
+ One of the most complicated aspects of setting up a Git server is user management.
+-If you want some repositories to be read-only for certain users and read/write for others, access and permissions can be a bit more difficult to arrange.
++If you want some repositories to be read-only to certain users and read/write to others, access and permissions can be a bit more difficult to arrange.
+ 
+ ===== SSH Access
+ 
+-(((serving repositories, SSH)))
+ If you have a server to which all your developers already have SSH access, it's generally easiest to set up your first repository there, because you have to do almost no work (as we covered in the last section).
+-If you want more complex access control type permissions on your repositories, you can handle them with the normal filesystem permissions of your server's operating system.
++If you want more complex access control type permissions on your repositories, you can handle them with the normal filesystem permissions of the operating system your server runs.
+ 
+-If you want to place your repositories on a server that doesn't have accounts for everyone on your team for whom you want to grant write access, then you must set up SSH access for them.
++If you want to place your repositories on a server that doesn't have accounts for everyone on your team whom you want to have write access, then you must set up SSH access for them.
+ We assume that if you have a server with which to do this, you already have an SSH server installed, and that's how you're accessing the server.
+ 
+ There are a few ways you can give access to everyone on your team.
+ The first is to set up accounts for everybody, which is straightforward but can be cumbersome.
+-You may not want to run `adduser` (or the possible alternative `useradd`) and have to set temporary passwords for every new user.
++You may not want to run `adduser` and set temporary passwords for every user.
+ 
+-A second method is to create a single 'git' user account on the machine, ask every user who is to have write access to send you an SSH public key, and add that key to the `~/.ssh/authorized_keys` file of that new 'git' account.
+-At that point, everyone will be able to access that machine via the 'git' account.
+-This doesn't affect the commit data in any way -- the SSH user you connect as doesn't affect the commits you've recorded.
++A second method is to create a single 'git' user on the machine, ask every user who is to have write access to send you an SSH public key, and add that key to the `~/.ssh/authorized_keys` file of your new 'git' user.
++At that point, everyone will be able to access that machine via the 'git' user.
++This doesn't affect the commit data in any way – the SSH user you connect as doesn't affect the commits you've recorded.
+ 
+ Another way to do it is to have your SSH server authenticate from an LDAP server or some other centralized authentication source that you may already have set up.
+ As long as each user can get shell access on the machine, any SSH authentication mechanism you can think of should work.
+diff -au ../../git/progit2/progit2/book/04-git-server/sections/gitlab.asc /tmp/book/04-git-server/sections/gitlab.asc.tmp
+--- ../../git/progit2/progit2/book/04-git-server/sections/gitlab.asc	2020-09-07 09:33:11.247683703 +0900
++++ /tmp/book/04-git-server/sections/gitlab.asc.tmp	2020-10-25 09:24:25.706969072 +0900
+@@ -2,63 +2,60 @@
+ 
+ (((serving repositories, GitLab)))(((GitLab)))
+ GitWeb is pretty simplistic though.
+-If you're looking for a modern, fully featured Git server, there are several open source solutions out there that you can install instead.
+-As GitLab is one of the popular ones, we'll cover installing and using it as an example.
+-This is harder than the GitWeb option and will require more maintenance, but it is a fully featured option.
++If you're looking for a more modern, fully featured Git server, there are some several open source solutions out there that you can install instead.
++As GitLab is one of the more popular ones, we'll cover installing and using it as an example.
++This is a bit more complex than the GitWeb option and likely requires more maintenance, but it is a much more fully featured option.
+ 
+ ==== Installation
+ 
+-GitLab is a database-backed web application, so its installation is more involved than some other Git servers.
+-Fortunately, this process is well-documented and supported.
+-GitLab strongly recommends installing GitLab on your server via the official Omnibus GitLab package.
+-
+-The other installation options are:
+-
+-* GitLab Helm chart, for use with Kubernetes.
+-* Dockerized GitLab packages for use with Docker.
+-* From the source files.
+-* Cloud provider such as AWS, Google Cloud Platform, Azure, OpenShift and Digital Ocean.
++GitLab is a database-backed web application, so its installation is a bit more involved than some other git servers.
++Fortunately, this process is very well-documented and supported.
+ 
+-For more information read the https://gitlab.com/gitlab-org/gitlab-foss/-/blob/master/README.md[GitLab Community Edition (CE) readme].
++There are a few methods you can pursue to install GitLab.
++To get something up and running quickly, you can download a virtual machine image or a one-click installer from https://bitnami.com/stack/gitlab[], and tweak the configuration to match your particular environment.(((bitnami)))
++One nice touch Bitnami has included is the login screen (accessed by typing alt-→); it tells you the IP address and default username and password for the installed GitLab.
++
++.The Bitnami GitLab virtual machine login screen.
++image::images/bitnami.png[The Bitnami GitLab virtual machine login screen.]
++
++For anything else, follow the guidance in the GitLab Community Edition readme, which can be found at https://gitlab.com/gitlab-org/gitlab-ce/tree/master[].
++There you'll find assistance for installing GitLab using Chef recipes, a virtual machine on Digital Ocean, and RPM and DEB packages (which, as of this writing, are in beta).
++There's also ``unofficial'' guidance on getting GitLab running with non-standard operating systems and databases, a fully-manual installation script, and many other topics.
+ 
+ ==== Administration
+ 
+ GitLab's administration interface is accessed over the web.
+-Simply point your browser to the hostname or IP address where GitLab is installed, and log in as the admin user.
+-The default username is `[e-mail]`, and the default password is `5iveL!fe` (which you must change right away).
+-After you've logged in, click the ``Admin area'' icon in the menu at the top right.
+-
+-[[gitlab_menu]]
+-.The ``Admin area'' item in the GitLab menu
+-image::images/gitlab-menu.png[The ``Admin area'' item in the GitLab menu]
++Simply point your browser to the hostname or IP address where GitLab is installed, and log in as an admin user.
++The default username is `[e-mail]`, and the default password is `5iveL!fe` (which you will be prompted to change as soon as you enter it).
++Once logged in, click the ``Admin area'' icon in the menu at the top right.
++
++.The ``Admin area'' item in the GitLab menu.
++image::images/gitlab-menu.png[The ``Admin area'' item in the GitLab menu.]
+ 
+ ===== Users
+ 
+-Everybody using your GitLab server must have an user account.
+-User accounts are quite simple, they mainly contain personal information attached to login data.
+-Each user account has a *namespace*, which is a logical grouping of projects that belong to that user.
+-If the user +jane+ had a project named +project+, that project's url would be `http://server/jane/project`.
+-
+-[[gitlab_users]]
+-.The GitLab user administration screen
+-image::images/gitlab-users.png[The GitLab user administration screen]
++Users in GitLab are accounts that correspond to people.
++User accounts don't have a lot of complexity; mainly it's a collection of personal information attached to login data.
++Each user account comes with a *namespace*, which is a logical grouping of projects that belong to that user.
++If the user +jane+ had a project named +project+, that project's url would be http://server/jane/project[].
++
++.The GitLab user administration screen.
++image::images/gitlab-users.png[The GitLab user administration screen.]
+ 
+-You can remove a user account in two ways:
++Removing a user can be done in two ways.
+ ``Blocking'' a user prevents them from logging into the GitLab instance, but all of the data under that user's namespace will be preserved, and commits signed with that user's email address will still link back to their profile.
+ 
+ ``Destroying'' a user, on the other hand, completely removes them from the database and filesystem.
+ All projects and data in their namespace is removed, and any groups they own will also be removed.
+-This is obviously a much more permanent and destructive action, and you will rarely need it.
++This is obviously a much more permanent and destructive action, and its uses are rare.
+ 
+-[[_gitlab_groups_section]]
+ ===== Groups
+ 
+-A GitLab group is a collection of projects, along with data about how users can access those projects.
+-Each group has a project namespace (the same way that users do), so if the group +training+ has a project +materials+, its url would be `http://server/training/materials`.
++A GitLab group is an assemblage of projects, along with data about how users can access those projects.
++Each group has a project namespace (the same way that users do), so if the group +training+ has a project +materials+, its url would be http://server/training/materials[].
+ 
+-[[gitlab_groups]]
+-.The GitLab group administration screen
+-image::images/gitlab-groups.png[The GitLab group administration screen]
++.The GitLab group administration screen.
++image::images/gitlab-groups.png[The GitLab group administration screen.]
+ 
+ Each group is associated with a number of users, each of which has a level of permissions for the group's projects and the group itself.
+ These range from ``Guest'' (issues and chat only) to ``Owner'' (full control of the group, its members, and its projects).
+@@ -66,27 +63,27 @@
+ 
+ ===== Projects
+ 
+-A GitLab project roughly corresponds to a single Git repository.
++A GitLab project roughly corresponds to a single git repository.
+ Every project belongs to a single namespace, either a user or a group.
+-If the project belongs to a user, the owner of the project has direct control over who has access to the project; if the project belongs to a group, the group's user-level permissions will take effect.
++If the project belongs to a user, the owner of the project has direct control over who has access to the project; if the project belongs to a group, the group's user-level permissions will also take effect.
+ 
+-Every project has a visibility level, which controls who has read access to that project's pages and repository.
++Every project also has a visibility level, which controls who has read access to that project's pages and repository.
+ If a project is _Private_, the project's owner must explicitly grant access to specific users.
+ An _Internal_ project is visible to any logged-in user, and a _Public_ project is visible to anyone.
+-Note that this controls both `git fetch` access as well as access to the web UI for that project.
++Note that this controls both git ``fetch'' access as well as access to the web UI for that project.
+ 
+ ===== Hooks
+ 
+ GitLab includes support for hooks, both at a project or system level.
+ For either of these, the GitLab server will perform an HTTP POST with some descriptive JSON whenever relevant events occur.
+-This is a great way to connect your Git repositories and GitLab instance to the rest of your development automation, such as CI servers, chat rooms, or deployment tools.
++This is a great way to connect your git repositories and GitLab instance to the rest of your development automation, such as CI servers, chat rooms, or deployment tools.
+ 
+ ==== Basic Usage
+ 
+ The first thing you'll want to do with GitLab is create a new project.
+-You can do this by clicking on the ``+'' icon on the toolbar.
++This is accomplished by clicking the ``+'' icon on the toolbar.
+ You'll be asked for the project's name, which namespace it should belong to, and what its visibility level should be.
+-Most of what you specify here isn't permanent, and can be changed later through the settings interface.
++Most of what you specify here isn't permanent, and can be re-adjusted later through the settings interface.
+ Click ``Create Project'', and you're done.
+ 
+ Once the project exists, you'll probably want to connect it with a local Git repository.
+@@ -94,31 +91,21 @@
+ The URLs are visible at the top of the project's home page.
+ For an existing local repository, this command will create a remote named `gitlab` to the hosted location:
+ 
+-[source,console]
+-----
+-$ git remote add gitlab https://server/namespace/project.git
+-----
+-
+ If you don't have a local copy of the repository, you can simply do this:
+ 
+-[source,console]
+-----
+-$ git clone https://server/namespace/project.git
+-----
+-
+ The web UI provides access to several useful views of the repository itself.
+ Each project's home page shows recent activity, and links along the top will lead you to views of the project's files and commit log.
+ 
+ ==== Working Together
+ 
+-The simplest way of working together on a GitLab project is by giving each user direct push access to the Git repository.
+-You can add a user to a project by going to the ``Members'' section of that project's settings, and associating the new user with an access level (the different access levels are discussed a bit in <<_gitlab_groups_section>>).
+-By giving a user an access level of ``Developer'' or above, that user can push commits and branches directly to the repository.
++The simplest way of working together on a GitLab project is by giving another user direct push access to the git repository.
++You can add a user to a project by going to the ``Members'' section of that project's settings, and associating the new user with an access level (the different access levels are discussed a bit in <<r_gitlab_groups_section>>).
++By giving a user an access level of ``Developer'' or above, that user can push commits and branches directly to the repository with impunity.
+ 
+ Another, more decoupled way of collaboration is by using merge requests.
+ This feature enables any user that can see a project to contribute to it in a controlled way.
+ Users with direct access can simply create a branch, push commits to it, and open a merge request from their branch back into `master` or any other branch.
+-Users who don't have push permissions for a repository can ``fork'' it to create their own copy, push commits to _their_ copy, and open a merge request from their fork back to the main project.
++Users who don't have push permissions for a repository can ``fork'' it (create their own copy), push commits to _that_ copy, and open a merge request from their fork back to the main project.
+ This model allows the owner to be in full control of what goes into the repository and when, while allowing contributions from untrusted users.
+ 
+ Merge requests and issues are the main units of long-lived discussion in GitLab.
+@@ -126,4 +113,4 @@
+ Both can be assigned to users, or organized into milestones.
+ 
+ This section is focused mainly on the Git-related features of GitLab, but as a mature project, it provides many other features to help your team work together, such as project wikis and system maintenance tools.
+-One benefit to GitLab is that, once the server is set up and running, you'll rarely need to tweak a configuration file or access the server via SSH; most administration and general usage can be done through the in-browser interface.
++One benefit to GitLab is that, once the server is set up and running, you'll rarely need to tweak a configuration file or access the server via SSH; most administration and general usage can be accomplished through the in-browser interface.
+diff -au ../../git/progit2/progit2/book/04-git-server/sections/gitweb.asc /tmp/book/04-git-server/sections/gitweb.asc.tmp
+--- ../../git/progit2/progit2/book/04-git-server/sections/gitweb.asc	2020-07-04 16:36:46.723685453 +0900
++++ /tmp/book/04-git-server/sections/gitweb.asc.tmp	2020-10-25 09:24:25.710969260 +0900
+@@ -4,67 +4,25 @@
+ Now that you have basic read/write and read-only access to your project, you may want to set up a simple web-based visualizer.
+ Git comes with a CGI script called GitWeb that is sometimes used for this.
+ 
+-[[gitweb]]
+-.The GitWeb web-based user interface
+-image::images/git-instaweb.png[The GitWeb web-based user interface]
++.GitWeb のユーザーインターフェイス
++image::images/git-instaweb.png[GitWeb のユーザーインターフェイス]
+ 
+-If you want to check out what GitWeb would look like for your project, Git comes with a command to fire up a temporary instance if you have a lightweight web server on your system like `lighttpd` or `webrick`.
++If you want to check out what GitWeb would look like for your project, Git comes with a command to fire up a temporary instance if you have a lightweight server on your system like `lighttpd` or `webrick`.
+ On Linux machines, `lighttpd` is often installed, so you may be able to get it to run by typing `git instaweb` in your project directory.
+ If you're running a Mac, Leopard comes preinstalled with Ruby, so `webrick` may be your best bet.
+ To start `instaweb` with a non-lighttpd handler, you can run it with the `--httpd` option.(((git commands, instaweb)))
+ 
+-[source,console]
+-----
+-$ git instaweb --httpd=webrick
+-[2009-02-21 10:02:21] INFO  WEBrick 1.3.1
+-[2009-02-21 10:02:21] INFO  ruby 1.8.6 (2008-03-03) [universal-darwin9.0]
+-----
+-
+ That starts up an HTTPD server on port 1234 and then automatically starts a web browser that opens on that page.
+ It's pretty easy on your part.
+ When you're done and want to shut down the server, you can run the same command with the `--stop` option:
+ 
+-[source,console]
+-----
+-$ git instaweb --httpd=webrick --stop
+-----
+-
+ If you want to run the web interface on a server all the time for your team or for an open source project you're hosting, you'll need to set up the CGI script to be served by your normal web server.
+-Some Linux distributions have a `gitweb` package that you may be able to install via `apt` or `dnf`, so you may want to try that first.
++Some Linux distributions have a `gitweb` package that you may be able to install via `apt` or `yum`, so you may want to try that first.
+ We'll walk through installing GitWeb manually very quickly.
+ First, you need to get the Git source code, which GitWeb comes with, and generate the custom CGI script:
+ 
+-[source,console]
+-----
+-$ git clone git://git.kernel.org/pub/scm/git/git.git
+-$ cd git/
+-$ make GITWEB_PROJECTROOT="/srv/git" prefix=/usr gitweb
+-    SUBDIR gitweb
+-    SUBDIR ../
+-make[2]: `GIT-VERSION-FILE' is up to date.
+-    GEN gitweb.cgi
+-    GEN static/gitweb.js
+-$ sudo cp -Rf gitweb /var/www/
+-----
+-
+ Notice that you have to tell the command where to find your Git repositories with the `GITWEB_PROJECTROOT` variable.
+ Now, you need to make Apache use CGI for that script, for which you can add a VirtualHost:
+ 
+-[source,console]
+-----
+-<VirtualHost *:80>
+-    ServerName gitserver
+-    DocumentRoot /var/www/gitweb
+-    <Directory /var/www/gitweb>
+-        Options +ExecCGI +FollowSymLinks +SymLinksIfOwnerMatch
+-        AllowOverride All
+-        order allow,deny
+-        Allow from all
+-        AddHandler cgi-script cgi
+-        DirectoryIndex gitweb.cgi
+-    </Directory>
+-</VirtualHost>
+-----
+-
+ Again, GitWeb can be served with any CGI or Perl capable web server; if you prefer to use something else, it shouldn't be difficult to set up.
+ At this point, you should be able to visit `http://gitserver/` to view your repositories online.
+diff -au ../../git/progit2/progit2/book/04-git-server/sections/hosted.asc /tmp/book/04-git-server/sections/hosted.asc.tmp
+--- ../../git/progit2/progit2/book/04-git-server/sections/hosted.asc	2020-07-04 16:36:46.725685477 +0900
++++ /tmp/book/04-git-server/sections/hosted.asc.tmp	2020-10-25 09:24:25.715969496 +0900
+@@ -5,6 +5,6 @@
+ Even if you set up and run your own server internally, you may still want to use a public hosting site for your open source code – it's generally easier for the open source community to find and help you with.
+ 
+ These days, you have a huge number of hosting options to choose from, each with different advantages and disadvantages.
+-To see an up-to-date list, check out the GitHosting page on the main Git wiki at https://git.wiki.kernel.org/index.php/GitHosting[].
++To see an up-to-date list, check out the GitHosting page on the main Git wiki at https://git.wiki.kernel.org/index.php/GitHosting[]
+ 
+ We'll cover using GitHub in detail in <<ch06-github#ch06-github>>, as it is the largest Git host out there and you may need to interact with projects hosted on it in any case, but there are dozens more to choose from should you not want to set up your own Git server.
+diff -au ../../git/progit2/progit2/book/04-git-server/sections/protocols.asc /tmp/book/04-git-server/sections/protocols.asc.tmp
+--- ../../git/progit2/progit2/book/04-git-server/sections/protocols.asc	2020-07-04 16:36:46.726685489 +0900
++++ /tmp/book/04-git-server/sections/protocols.asc.tmp	2020-10-25 09:24:25.720969732 +0900
+@@ -1,55 +1,39 @@
+ === The Protocols
+ 
+-Git can use four distinct protocols to transfer data: Local, HTTP, Secure Shell (SSH) and Git.
++Git can use four major protocols to transfer data: Local, HTTP, Secure Shell (SSH) and Git.
+ Here we'll discuss what they are and in what basic circumstances you would want (or not want) to use them.
+ 
+ ==== Local Protocol
+ 
+-(((protocols, local)))
+-The most basic is the _Local protocol_, in which the remote repository is in another directory on the same host.
+-This is often used if everyone on your team has access to a shared filesystem such as an https://en.wikipedia.org/wiki/Network_File_System[NFS] mount, or in the less likely case that everyone logs in to the same computer.
++The most basic is the _Local protocol_, in which the remote repository is in another directory on disk.
++This is often used if everyone on your team has access to a shared filesystem such as an NFS mount, or in the less likely case that everyone logs in to the same computer.
+ The latter wouldn't be ideal, because all your code repository instances would reside on the same computer, making a catastrophic loss much more likely.
+ 
+ If you have a shared mounted filesystem, then you can clone, push to, and pull from a local file-based repository.
+-To clone a repository like this, or to add one as a remote to an existing project, use the path to the repository as the URL.
++To clone a repository like this or to add one as a remote to an existing project, use the path to the repository as the URL.
+ For example, to clone a local repository, you can run something like this:
+ 
+-[source,console]
+-----
+-$ git clone /srv/git/project.git
+-----
+-
+ Or you can do this:
+ 
+-[source,console]
+-----
+-$ git clone file:///srv/git/project.git
+-----
+-
+ Git operates slightly differently if you explicitly specify `file://` at the beginning of the URL.
+ If you just specify the path, Git tries to use hardlinks or directly copy the files it needs.
+-If you specify `file://`, Git fires up the processes that it normally uses to transfer data over a network, which is generally much less efficient.
+-The main reason to specify the `file://` prefix is if you want a clean copy of the repository with extraneous references or objects left out -- generally after an import from another VCS or something similar (see <<ch10-git-internals#ch10-git-internals>> for maintenance tasks).
++If you specify `file://`, Git fires up the processes that it normally uses to transfer data over a network which is generally a lot less efficient method of transferring the data.
++The main reason to specify the `file://` prefix is if you want a clean copy of the repository with extraneous references or objects left out – generally after an import from another version-control system or something similar (see <<ch10-git-internals#ch10-git-internals>> for maintenance tasks).
+ We'll use the normal path here because doing so is almost always faster.
+ 
+ To add a local repository to an existing Git project, you can run something like this:
+ 
+-[source,console]
+-----
+-$ git remote add local_proj /srv/git/project.git
+-----
+-
+-Then, you can push to and pull from that remote via your new remote name `local_proj` as though you were doing so over a network.
++Then, you can push to and pull from that remote as though you were doing so over a network.
+ 
+ ===== The Pros
+ 
+ The pros of file-based repositories are that they're simple and they use existing file permissions and network access.
+ If you already have a shared filesystem to which your whole team has access, setting up a repository is very easy.
+ You stick the bare repository copy somewhere everyone has shared access to and set the read/write permissions as you would for any other shared directory.
+-We'll discuss how to export a bare repository copy for this purpose in <<ch04-git-on-the-server#_getting_git_on_a_server>>.
++We'll discuss how to export a bare repository copy for this purpose in <<r_git_on_the_server>>.
+ 
+ This is also a nice option for quickly grabbing work from someone else's working repository.
+-If you and a co-worker are working on the same project and they want you to check something out, running a command like `git pull /home/john/project` is often easier than them pushing to a remote server and you subsequently fetching from it.
++If you and a co-worker are working on the same project and they want you to check something out, running a command like `git pull /home/john/project` is often easier than them pushing to a remote server and you pulling down.
+ 
+ ===== The Cons
+ 
+@@ -61,59 +45,39 @@
+ A repository on NFS is often slower than the repository over SSH on the same server, allowing Git to run off local disks on each system.
+ 
+ Finally, this protocol does not protect the repository against accidental damage.
+-Every user has full shell access to the ``remote'' directory, and there is nothing preventing them from changing or removing internal Git files and corrupting the repository.
++Every user has full shell access to the "remote" directory, and there is nothing preventing them from changing or removing internal Git files and corrupting the repository.
+ 
+ ==== The HTTP Protocols
+ 
+-Git can communicate over HTTP using two different modes.
+-Prior to Git 1.6.6, there was only one way it could do this which was very simple and generally read-only.
+-In version 1.6.6, a new, smarter protocol was introduced that involved Git being able to intelligently negotiate data transfer in a manner similar to how it does over SSH.
++Git can communicate over HTTP in two different modes.
++Prior to Git 1.6.6 there was only one way it could do this which was very simple and generally read-only.
++In version 1.6.6 a new, smarter protocol was introduced that involved Git being able to intelligently negotiate data transfer in a manner similar to how it does over SSH.
+ In the last few years, this new HTTP protocol has become very popular since it's simpler for the user and smarter about how it communicates.
+-The newer version is often referred to as the _Smart_ HTTP protocol and the older way as _Dumb_ HTTP.
+-We'll cover the newer Smart HTTP protocol first.
++The newer version is often referred to as the ``Smart'' HTTP protocol and the older way as ``Dumb'' HTTP.
++We'll cover the newer ``smart'' HTTP protocol first.
+ 
+-===== Smart HTTP
+-
+-(((protocols, smart HTTP)))
+-Smart HTTP operates very similarly to the SSH or Git protocols but runs over standard HTTPS ports and can use various HTTP authentication mechanisms, meaning it's often easier on the user than something like SSH, since you can use things like username/password authentication rather than having to set up SSH keys.
++The ``smart'' HTTP protocol operates very similarly to the SSH or Git protocols but runs over standard HTTP/S ports and can use various HTTP authentication mechanisms, meaning it's often easier on the user than something like SSH, since you can use things like username/password basic authentication rather than having to set up SSH keys.
+ 
+ It has probably become the most popular way to use Git now, since it can be set up to both serve anonymously like the `git://` protocol, and can also be pushed over with authentication and encryption like the SSH protocol.
+ Instead of having to set up different URLs for these things, you can now use a single URL for both.
+ If you try to push and the repository requires authentication (which it normally should), the server can prompt for a username and password.
+ The same goes for read access.
+ 
+-In fact, for services like GitHub, the URL you use to view the repository online (for example, https://github.com/schacon/simplegit[]) is the same URL you can use to clone and, if you have access, push over.
+-
+-===== Dumb HTTP
++In fact, for services like GitHub, the URL you use to view the repository online (for example, ``https://github.com/schacon/simplegit[]'') is the same URL you can use to clone and, if you have access, push over.
+ 
+-(((protocols, dumb HTTP)))
+-If the server does not respond with a Git HTTP smart service, the Git client will try to fall back to the simpler _Dumb_ HTTP protocol.
++If the server does not respond with a Git HTTP smart service, the Git client will try to fall back to the simpler ``dumb'' HTTP protocol.
+ The Dumb protocol expects the bare Git repository to be served like normal files from the web server.
+-The beauty of Dumb HTTP is the simplicity of setting it up.
+-Basically, all you have to do is put a bare Git repository under your HTTP document root and set up a specific `post-update` hook, and you're done (See <<ch08-customizing-git#_git_hooks>>).
++The beauty of the Dumb HTTP protocol is the simplicity of setting it up.
++Basically, all you have to do is put a bare Git repository under your HTTP document root and set up a specific `post-update` hook, and you're done (See <<ch08-customizing-git#r_git_hooks>>).
+ At that point, anyone who can access the web server under which you put the repository can also clone your repository.
+ To allow read access to your repository over HTTP, do something like this:
+ 
+-[source,console]
+-----
+-$ cd /var/www/htdocs/
+-$ git clone --bare /path/to/git_project gitproject.git
+-$ cd gitproject.git
+-$ mv hooks/post-update.sample hooks/post-update
+-$ chmod a+x hooks/post-update
+-----
+-
+ That's all.(((hooks, post-update)))
+ The `post-update` hook that comes with Git by default runs the appropriate command (`git update-server-info`) to make HTTP fetching and cloning work properly.
+-This command is run when you push to this repository (over SSH perhaps); then, other people can clone via something like:
+-
+-[source,console]
+-----
+-$ git clone https://example.com/gitproject.git
+-----
++This command is run when you push to this repository (over SSH perhaps); then, other people can clone via something like
+ 
+-In this particular case, we're using the `/var/www/htdocs` path that is common for Apache setups, but you can use any static web server -- just put the bare repository in its path.
+-The Git data is served as basic static files (see the <<ch10-git-internals#ch10-git-internals>> chapter for details about exactly how it's served).
++In this particular case, we're using the `/var/www/htdocs` path that is common for Apache setups, but you can use any static web server – just put the bare repository in its path.
++The Git data is served as basic static files (see <<ch10-git-internals#ch10-git-internals>> for details about exactly how it's served).
+ 
+ Generally you would either choose to run a read/write Smart HTTP server or simply have the files accessible as read-only in the Dumb manner.
+ It's rare to run a mix of the two services.
+@@ -129,69 +93,57 @@
+ 
+ You can also serve your repositories read-only over HTTPS, which means you can encrypt the content transfer; or you can go so far as to make the clients use specific signed SSL certificates.
+ 
+-Another nice thing is that HTTP and HTTPS are such commonly used protocols that corporate firewalls are often set up to allow traffic through their ports.
++Another nice thing is that HTTP/S are such commonly used protocols that corporate firewalls are often set up to allow traffic through these ports.
+ 
+ ===== The Cons
+ 
+-Git over HTTPS can be a little more tricky to set up compared to SSH on some servers.
+-Other than that, there is very little advantage that other protocols have over Smart HTTP for serving Git content.
++Git over HTTP/S can be a little more tricky to set up compared to SSH on some servers.
++Other than that, there is very little advantage that other protocols have over the ``Smart'' HTTP protocol for serving Git.
+ 
+ If you're using HTTP for authenticated pushing, providing your credentials is sometimes more complicated than using keys over SSH.
+-There are, however, several credential caching tools you can use, including Keychain access on macOS and Credential Manager on Windows, to make this pretty painless.
+-Read <<ch07-git-tools#_credential_caching>> to see how to set up secure HTTP password caching on your system.
++There are however several credential caching tools you can use, including Keychain access on OSX and Credential Manager on Windows, to make this pretty painless.
++Read <<ch07-git-tools#r_credential_caching>> to see how to set up secure HTTP password caching on your system.
+ 
+ ==== The SSH Protocol
+ 
+-(((protocols, SSH)))
+ A common transport protocol for Git when self-hosting is over SSH.
+-This is because SSH access to servers is already set up in most places -- and if it isn't, it's easy to do.
+-SSH is also an authenticated network protocol and, because it's ubiquitous, it's generally easy to set up and use.
++This is because SSH access to servers is already set up in most places – and if it isn't, it's easy to do.
++SSH is also an authenticated network protocol; and because it's ubiquitous, it's generally easy to set up and use.
+ 
+-To clone a Git repository over SSH, you can specify an `ssh://` URL like this:
+-
+-[source,console]
+-----
+-$ git clone ssh://[user@]server/project.git
+-----
++To clone a Git repository over SSH, you can specify ssh:// URL like this:
+ 
+ Or you can use the shorter scp-like syntax for the SSH protocol:
+ 
+-[source,console]
+-----
+-$ git clone [user@]server:project.git
+-----
+-
+-In both cases above, if you don't specify the optional username, Git assumes the user you're currently logged in as.
++You can also not specify a user, and Git assumes the user you're currently logged in as.
+ 
+ ===== The Pros
+ 
+ The pros of using SSH are many.
+-First, SSH is relatively easy to set up -- SSH daemons are commonplace, many network admins have experience with them, and many OS distributions are set up with them or have tools to manage them.
+-Next, access over SSH is secure -- all data transfer is encrypted and authenticated.
+-Last, like the HTTPS, Git and Local protocols, SSH is efficient, making the data as compact as possible before transferring it.
++First, SSH is relatively easy to set up – SSH daemons are commonplace, many network admins have experience with them, and many OS distributions are set up with them or have tools to manage them.
++Next, access over SSH is secure – all data transfer is encrypted and authenticated.
++Last, like the HTTP/S, Git and Local protocols, SSH is efficient, making the data as compact as possible before transferring it.
+ 
+ ===== The Cons
+ 
+-The negative aspect of SSH is that it doesn't support anonymous access to your Git repository.
+-If you're using SSH, people _must_ have SSH access to your machine, even in a read-only capacity, which doesn't make SSH conducive to open source projects for which people might simply want to clone your repository to examine it.
++The negative aspect of SSH is that you can't serve anonymous access of your repository over it.
++People must have access to your machine over SSH to access it, even in a read-only capacity, which doesn't make SSH access conducive to open source projects.
+ If you're using it only within your corporate network, SSH may be the only protocol you need to deal with.
+-If you want to allow anonymous read-only access to your projects and also want to use SSH, you'll have to set up SSH for you to push over but something else for others to fetch from.
++If you want to allow anonymous read-only access to your projects and also want to use SSH, you’ll have to set up SSH for you to push over but something else for others to fetch over.
+ 
+ ==== The Git Protocol
+ 
+-(((protocols, git)))
+-Finally, we have the Git protocol.
++Next is the Git protocol.
+ This is a special daemon that comes packaged with Git; it listens on a dedicated port (9418) that provides a service similar to the SSH protocol, but with absolutely no authentication.
+-In order for a repository to be served over the Git protocol, you must create a `git-daemon-export-ok` file -- the daemon won't serve a repository without that file in it -- but, other than that, there is no security.
+-Either the Git repository is available for everyone to clone, or it isn't.
++In order for a repository to be served over the Git protocol, you must create the `git-daemon-export-ok` file – the daemon won't serve a repository without that file in it – but other than that there is no security.
++Either the Git repository is available for everyone to clone or it isn't.
+ This means that there is generally no pushing over this protocol.
+-You can enable push access but, given the lack of authentication, anyone on the internet who finds your project's URL could push to that project.
++You can enable push access; but given the lack of authentication, if you turn on push access, anyone on the internet who finds your project's URL could push to your project.
+ Suffice it to say that this is rare.
+ 
+ ===== The Pros
+ 
+ The Git protocol is often the fastest network transfer protocol available.
+-If you're serving a lot of traffic for a public project or serving a very large project that doesn't require user authentication for read access, it's likely that you'll want to set up a Git daemon to serve your project.
++If you’re serving a lot of traffic for a public project or serving a very large project that doesn't require user authentication for read access, it’s likely that you'll want to set up a Git daemon to serve your project.
+ It uses the same data-transfer mechanism as the SSH protocol but without the encryption and authentication overhead.
+ 
+ ===== The Cons
+@@ -200,6 +152,6 @@
+ It's generally undesirable for the Git protocol to be the only access to your project.
+ Generally, you'll pair it with SSH or HTTPS access for the few developers who have push (write) access and have everyone else use `git://` for read-only access.
+ It's also probably the most difficult protocol to set up.
+-It must run its own daemon, which requires `xinetd` or `systemd` configuration or the like, which isn't always a walk in the park.
++It must run its own daemon, which requires `xinetd` configuration or the like, which isn't always a walk in the park.
+ It also requires firewall access to port 9418, which isn't a standard port that corporate firewalls always allow.
+ Behind big corporate firewalls, this obscure port is commonly blocked.
+diff -au ../../git/progit2/progit2/book/04-git-server/sections/setting-up-server.asc /tmp/book/04-git-server/sections/setting-up-server.asc.tmp
+--- ../../git/progit2/progit2/book/04-git-server/sections/setting-up-server.asc	2020-06-28 16:44:50.927015646 +0900
++++ /tmp/book/04-git-server/sections/setting-up-server.asc.tmp	2020-10-25 09:24:25.727970062 +0900
+@@ -1,147 +1,40 @@
+-[[_setting_up_server]]
++[[r_setting_up_server]]
+ === Setting Up the Server
+ 
+ Let's walk through setting up SSH access on the server side.
+ In this example, you'll use the `authorized_keys` method for authenticating your users.
+ We also assume you're running a standard Linux distribution like Ubuntu.
+-
+-[NOTE]
+-====
+-A good deal of what is described here can be automated by using the `ssh-copy-id` command, rather than manually copying and installing public keys.
+-====
+-
+-First, you create a `git` user account and a `.ssh` directory for that user.
+-
+-[source,console]
+-----
+-$ sudo adduser git
+-$ su git
+-$ cd
+-$ mkdir .ssh && chmod 700 .ssh
+-$ touch .ssh/authorized_keys && chmod 600 .ssh/authorized_keys
+-----
++First, you create a `git` user and a `.ssh` directory for that user.
+ 
+ Next, you need to add some developer SSH public keys to the `authorized_keys` file for the `git` user.
+ Let's assume you have some trusted public keys and have saved them to temporary files.
+ Again, the public keys look something like this:
+ 
+-[source,console]
+-----
+-$ cat /tmp/id_rsa.john.pub
+-ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCB007n/ww+ouN4gSLKssMxXnBOvf9LGt4L
+-ojG6rs6hPB09j9R/T17/x4lhJA0F3FR1rP6kYBRsWj2aThGw6HXLm9/5zytK6Ztg3RPKK+4k
+-Yjh6541NYsnEAZuXz0jTTyAUfrtU3Z5E003C4oxOj6H0rfIF1kKI9MAQLMdpGW1GYEIgS9Ez
+-Sdfd8AcCIicTDWbqLAcU4UpkaX8KyGlLwsNuuGztobF8m72ALC/nLF6JLtPofwFBlgc+myiv
+-O7TCUSBdLQlgMVOFq1I2uPWQOkOWQAHukEOmfjy2jctxSDBQ220ymjaNsHT4kgtZg2AYYgPq
+-dAv8JggJICUvax2T9va5 gsg-keypair
+-----
+-
+ You just append them to the `git` user's `authorized_keys` file in its `.ssh` directory:
+ 
+-[source,console]
+-----
+-$ cat /tmp/id_rsa.john.pub >> ~/.ssh/authorized_keys
+-$ cat /tmp/id_rsa.josie.pub >> ~/.ssh/authorized_keys
+-$ cat /tmp/id_rsa.jessica.pub >> ~/.ssh/authorized_keys
+-----
+-
+ Now, you can set up an empty repository for them by running `git init` with the `--bare` option, which initializes the repository without a working directory:(((git commands, init, bare)))
+ 
+-[source,console]
+-----
+-$ cd /srv/git
+-$ mkdir project.git
+-$ cd project.git
+-$ git init --bare
+-Initialized empty Git repository in /srv/git/project.git/
+-----
+-
+ Then, John, Josie, or Jessica can push the first version of their project into that repository by adding it as a remote and pushing up a branch.
+ Note that someone must shell onto the machine and create a bare repository every time you want to add a project.
+ Let's use `gitserver` as the hostname of the server on which you've set up your `git` user and repository.
+ If you're running it internally, and you set up DNS for `gitserver` to point to that server, then you can use the commands pretty much as is (assuming that `myproject` is an existing project with files in it):
+ 
+-[source,console]
+-----
+-# on John's computer
+-$ cd myproject
+-$ git init
+-$ git add .
+-$ git commit -m 'Initial commit'
+-$ git remote add origin git@gitserver:/srv/git/project.git
+-$ git push origin master
+-----
+-
+ At this point, the others can clone it down and push changes back up just as easily:
+ 
+-[source,console]
+-----
+-$ git clone git@gitserver:/srv/git/project.git
+-$ cd project
+-$ vim README
+-$ git commit -am 'Fix for README file'
+-$ git push origin master
+-----
+-
+ With this method, you can quickly get a read/write Git server up and running for a handful of developers.
+ 
+ You should note that currently all these users can also log into the server and get a shell as the `git` user.
+-If you want to restrict that, you will have to change the shell to something else in the `/etc/passwd` file.
++If you want to restrict that, you will have to change the shell to something else in the `passwd` file.
+ 
+-You can easily restrict the `git` user account to only Git-related activities with a limited shell tool called `git-shell` that comes with Git.
+-If you set this as the `git` user account's login shell, then that account can't have normal shell access to your server.
+-To use this, specify `git-shell` instead of `bash` or `csh` for that account's login shell.
+-To do so, you must first add the full pathname of the `git-shell` command to `/etc/shells` if it's not already there:
+-
+-[source,console]
+-----
+-$ cat /etc/shells   # see if git-shell is already in there. If not...
+-$ which git-shell   # make sure git-shell is installed on your system.
+-$ sudo -e /etc/shells  # and add the path to git-shell from last command
+-----
+-
+-Now you can edit the shell for a user using `chsh <username> -s <shell>`:
+-
+-[source,console]
+-----
+-$ sudo chsh git -s $(which git-shell)
+-----
++You can easily restrict the `git` user to only doing Git activities with a limited shell tool called `git-shell` that comes with Git.
++If you set this as your `git` user's login shell, then the `git` user can't have normal shell access to your server.
++To use this, specify `git-shell` instead of bash or csh for your user's login shell.
++To do so, you must first add `git-shell` to `/etc/shells` if it's not already there:
+ 
+-Now, the `git` user can still use the SSH connection to push and pull Git repositories but can't shell onto the machine.
+-If you try, you'll see a login rejection like this:
++Now you can edit the shell for a user using `chsh <username>`:
+ 
+-[source,console]
+-----
+-$ ssh git@gitserver
+-fatal: Interactive git shell is not enabled.
+-hint: ~/git-shell-commands should exist and have read and execute access.
+-Connection to gitserver closed.
+-----
+-
+-At this point, users are still able to use SSH port forwarding to access any host the git server is able to reach.
+-If you want to prevent that, you can edit the `authorized_keys` file and prepend the following options to each key you'd like to restrict:
+-
+-[source,console]
+-----
+-no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty
+-----
+-
+-The result should look like this:
+-
+-[source,console]
+-----
+-$ cat ~/.ssh/authorized_keys
+-no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty ssh-rsa
+-AAAAB3NzaC1yc2EAAAADAQABAAABAQCB007n/ww+ouN4gSLKssMxXnBOvf9LGt4LojG6rs6h
+-PB09j9R/T17/x4lhJA0F3FR1rP6kYBRsWj2aThGw6HXLm9/5zytK6Ztg3RPKK+4kYjh6541N
+-YsnEAZuXz0jTTyAUfrtU3Z5E003C4oxOj6H0rfIF1kKI9MAQLMdpGW1GYEIgS9EzSdfd8AcC
+-IicTDWbqLAcU4UpkaX8KyGlLwsNuuGztobF8m72ALC/nLF6JLtPofwFBlgc+myivO7TCUSBd
+-LQlgMVOFq1I2uPWQOkOWQAHukEOmfjy2jctxSDBQ220ymjaNsHT4kgtZg2AYYgPqdAv8JggJ
+-ICUvax2T9va5 gsg-keypair
+-
+-no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty ssh-rsa
+-AAAAB3NzaC1yc2EAAAADAQABAAABAQDEwENNMomTboYI+LJieaAY16qiXiH3wuvENhBG...
+-----
++Now, the `git` user can only use the SSH connection to push and pull Git repositories and can't shell onto the machine.
++If you try, you'll see a login rejection like this:
+ 
+ Now Git network commands will still work just fine but the users won't be able to get a shell.
+ As the output states, you can also set up a directory in the `git` user's home directory that customizes the `git-shell` command a bit.
+diff -au ../../git/progit2/progit2/book/04-git-server/sections/smart-http.asc /tmp/book/04-git-server/sections/smart-http.asc.tmp
+--- ../../git/progit2/progit2/book/04-git-server/sections/smart-http.asc	2020-06-28 16:44:50.927015646 +0900
++++ /tmp/book/04-git-server/sections/smart-http.asc.tmp	2020-10-25 09:24:25.732970297 +0900
+@@ -1,62 +1,28 @@
+ === Smart HTTP
+ 
+ (((serving repositories, HTTP)))
+-We now have authenticated access through SSH and unauthenticated access through `git://`, but there is also a protocol that can do both at the same time.
++We now have authenticated access though SSH and unauthenticated access through `git://`, but there is also a protocol that can do both at the same time.
+ Setting up Smart HTTP is basically just enabling a CGI script that is provided with Git called `git-http-backend` on the server.(((git commands, "http-backend")))
+ This CGI will read the path and headers sent by a `git fetch` or `git push` to an HTTP URL and determine if the client can communicate over HTTP (which is true for any client since version 1.6.6).
+-If the CGI sees that the client is smart, it will communicate smartly with it; otherwise it will fall back to the dumb behavior (so it is backward compatible for reads with older clients).
++If the CGI sees that the client is smart, it will communicate smartly with it, otherwise it will fall back to the dumb behavior (so it is backward compatible for reads with older clients).
+ 
+ Let's walk through a very basic setup.
+ We'll set this up with Apache as the CGI server.
+ If you don't have Apache setup, you can do so on a Linux box with something like this:(((Apache)))
+ 
+-[source,console]
+-----
+-$ sudo apt-get install apache2 apache2-utils
+-$ a2enmod cgi alias env
+-----
+-
+-This also enables the `mod_cgi`, `mod_alias`, and `mod_env` modules, which are all needed for this to work properly.
+-
+-You'll also need to set the Unix user group of the `/srv/git` directories to `www-data` so your web server can read- and write-access the repositories, because the Apache instance running the CGI script will (by default) be running as that user:
+-
+-[source,console]
+-----
+-$ chgrp -R www-data /srv/git
+-----
++This also enables the `mod_cgi`, `mod_alias`, `mod_env`, and `mod_rewrite` modules, which are all needed for this to work properly.
+ 
+-Next we need to add some things to the Apache configuration to run the `git-http-backend` as the handler for anything coming into the `/git` path of your web server.
++You’ll also need to set the Unix user group of the `/opt/git` directories to `www-data` so your web server can read- and write-access the repositories, because the Apache instance running the CGI script will (by default) be running as that user:
+ 
+-[source,console]
+-----
+-SetEnv GIT_PROJECT_ROOT /srv/git
+-SetEnv GIT_HTTP_EXPORT_ALL
+-ScriptAlias /git/ /usr/lib/git-core/git-http-backend/
+-----
++Next we need to add some things to the Apache configuration to run the `git-http-backend` as the handler for anything coming into the `/git` path of your web server.
+ 
+ If you leave out `GIT_HTTP_EXPORT_ALL` environment variable, then Git will only serve to unauthenticated clients the repositories with the `git-daemon-export-ok` file in them, just like the Git daemon did.
+ 
+ Finally you'll want to tell Apache to allow requests to `git-http-backend` and make writes be authenticated somehow, possibly with an Auth block like this:
+ 
+-[source,console]
+-----
+-<Files "git-http-backend">
+-    AuthType Basic
+-    AuthName "Git Access"
+-    AuthUserFile /srv/git/.htpasswd
+-    Require expr !(%{QUERY_STRING} -strmatch '*service=git-receive-pack*' || %{REQUEST_URI} =~ m#/git-receive-pack$#)
+-    Require valid-user
+-</Files>
+-----
+-
+ That will require you to create a `.htpasswd` file containing the passwords of all the valid users.
+ Here is an example of adding a ``schacon'' user to the file:
+ 
+-[source,console]
+-----
+-$ htpasswd -c /srv/git/.htpasswd schacon
+-----
+-
+ There are tons of ways to have Apache authenticate users, you'll have to choose and implement one of them.
+ This is just the simplest example we could come up with.
+ You'll also almost certainly want to set this up over SSL so all this data is encrypted.
+@@ -66,7 +32,6 @@
+ It does not implement any authentication itself, but that can easily be controlled at the layer of the web server that invokes it.
+ You can do this with nearly any CGI-capable web server, so go with the one that you know best.
+ 
+-[NOTE]
+ ====
+-For more information on configuring authentication in Apache, check out the Apache docs here: https://httpd.apache.org/docs/current/howto/auth.html[]
++For more information on configuring authentication in Apache, check out the Apache docs here: http://httpd.apache.org/docs/current/howto/auth.html[]
+ ====
+diff -au ../../git/progit2/progit2/book/05-distributed-git/sections/contributing.asc /tmp/book/05-distributed-git/sections/contributing.asc.tmp
+--- ../../git/progit2/progit2/book/05-distributed-git/sections/contributing.asc	2020-08-29 09:58:24.050195768 +0900
++++ /tmp/book/05-distributed-git/sections/contributing.asc.tmp	2020-10-25 09:24:25.740970675 +0900
+@@ -1,12 +1,11 @@
+-[[_contributing_project]]
++[[r_contributing_project]]
+ === Contributing to a Project
+ 
+-(((contributing)))
+-The main difficulty with describing how to contribute to a project are the numerous variations on how to do that.
+-Because Git is very flexible, people can and do work together in many ways, and it's problematic to describe how you should contribute -- every project is a bit different.
++The main difficulty with describing how to contribute to a project is that there are a huge number of variations on how it's done.
++Because Git is very flexible, people can and do work together in many ways, and it's problematic to describe how you should contribute – every project is a bit different.
+ Some of the variables involved are active contributor count, chosen workflow, your commit access, and possibly the external contribution method.
+ 
+-The first variable is active contributor count -- how many users are actively contributing code to this project, and how often?
++The first variable is active contributor count – how many users are actively contributing code to this project, and how often?
+ In many instances, you'll have two or three developers with a few commits a day, or possibly less for somewhat dormant projects.
+ For larger companies or projects, the number of developers could be in the thousands, with hundreds or thousands of commits coming in each day.
+ This is important because with more and more developers, you run into more issues with making sure your code applies cleanly or can be easily merged.
+@@ -20,7 +19,7 @@
+ Are you involved in that process?
+ Is a lieutenant system in place, and do you have to submit your work to them first?
+ 
+-The next variable is your commit access.
++The next issue is your commit access.
+ The workflow required in order to contribute to a project is much different if you have write access to the project than if you don't.
+ If you don't have write access, how does the project prefer to accept contributed work?
+ Does it even have a policy?
+@@ -30,89 +29,75 @@
+ All these questions can affect how you contribute effectively to a project and what workflows are preferred or available to you.
+ We'll cover aspects of each of these in a series of use cases, moving from simple to more complex; you should be able to construct the specific workflows you need in practice from these examples.
+ 
+-[[_commit_guidelines]]
+ ==== Commit Guidelines
+ 
+ Before we start looking at the specific use cases, here's a quick note about commit messages.
+ Having a good guideline for creating commits and sticking to it makes working with Git and collaborating with others a lot easier.
+-The Git project provides a document that lays out a number of good tips for creating commits from which to submit patches -- you can read it in the Git source code in the `Documentation/SubmittingPatches` file.
++The Git project provides a document that lays out a number of good tips for creating commits from which to submit patches – you can read it in the Git source code in the `Documentation/SubmittingPatches` file.
+ 
+-(((git commands, diff, check)))
+-First, your submissions should not contain any whitespace errors.
+-Git provides an easy way to check for this -- before you commit, run `git diff --check`, which identifies possible whitespace errors and lists them for you.
++First, you don't want to submit any whitespace errors.
++Git provides an easy way to check for this – before you commit, run `git diff --check`, which identifies possible whitespace errors and lists them for you.
+ 
+-.Output of `git diff --check`
+-image::images/git-diff-check.png[Output of `git diff --check`]
++.Output of `git diff --check`.
++image::images/git-diff-check.png[Output of `git diff --check`.]
+ 
+ If you run that command before committing, you can tell if you're about to commit whitespace issues that may annoy other developers.
+ 
+ Next, try to make each commit a logically separate changeset.
+-If you can, try to make your changes digestible -- don't code for a whole weekend on five different issues and then submit them all as one massive commit on Monday.
++If you can, try to make your changes digestible – don't code for a whole weekend on five different issues and then submit them all as one massive commit on Monday.
+ Even if you don't commit during the weekend, use the staging area on Monday to split your work into at least one commit per issue, with a useful message per commit.
+-If some of the changes modify the same file, try to use `git add --patch` to partially stage files (covered in detail in <<ch07-git-tools#_interactive_staging>>).
++If some of the changes modify the same file, try to use `git add --patch` to partially stage files (covered in detail in <<ch07-git-tools#r_interactive_staging>>).
+ The project snapshot at the tip of the branch is identical whether you do one commit or five, as long as all the changes are added at some point, so try to make things easier on your fellow developers when they have to review your changes.
+-
+ This approach also makes it easier to pull out or revert one of the changesets if you need to later.
+-<<ch07-git-tools#_rewriting_history>> describes a number of useful Git tricks for rewriting history and interactively staging files -- use these tools to help craft a clean and understandable history before sending the work to someone else.
++<<ch07-git-tools#r_rewriting_history>> describes a number of useful Git tricks for rewriting history and interactively staging files – use these tools to help craft a clean and understandable history before sending the work to someone else.
+ 
+ The last thing to keep in mind is the commit message.
+ Getting in the habit of creating quality commit messages makes using and collaborating with Git a lot easier.
+ As a general rule, your messages should start with a single line that's no more than about 50 characters and that describes the changeset concisely, followed by a blank line, followed by a more detailed explanation.
+-The Git project requires that the more detailed explanation include your motivation for the change and contrast its implementation with previous behavior -- this is a good guideline to follow.
+-Write your commit message in the imperative: "Fix bug" and not "Fixed bug" or "Fixes bug."
+-Here is a template you can follow, which we've lightly adapted from one https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html[originally written by Tim Pope]:
+-
+-[source,text]
+-----
+-Capitalized, short (50 chars or less) summary
+-
+-More detailed explanatory text, if necessary.  Wrap it to about 72
+-characters or so.  In some contexts, the first line is treated as the
+-subject of an email and the rest of the text as the body.  The blank
+-line separating the summary from the body is critical (unless you omit
+-the body entirely); tools like rebase will confuse you if you run the
+-two together.
+-
+-Write your commit message in the imperative: "Fix bug" and not "Fixed bug"
+-or "Fixes bug."  This convention matches up with commit messages generated
+-by commands like git merge and git revert.
++The Git project requires that the more detailed explanation include your motivation for the change and contrast its implementation with previous behavior – this is a good guideline to follow.
++It's also a good idea to use the imperative present tense in these messages.
++In other words, use commands.
++Instead of ``I added tests for'' or ``Adding tests for,'' use ``Add tests for.''
++Here is a template originally written by Tim Pope:
++
++----
++Short (50 chars or less) summary of changes
++
++More detailed explanatory text, if necessary.  Wrap it to
++about 72 characters or so.  In some contexts, the first
++line is treated as the subject of an email and the rest of
++the text as the body.  The blank line separating the
++summary from the body is critical (unless you omit the body
++entirely); tools like rebase can get confused if you run
++the two together.
+ 
+ Further paragraphs come after blank lines.
+ 
+-- Bullet points are okay, too
+-
+-- Typically a hyphen or asterisk is used for the bullet, followed by a
+-  single space, with blank lines in between, but conventions vary here
++  - Bullet points are okay, too
+ 
+-- Use a hanging indent
++  - Typically a hyphen or asterisk is used for the bullet,
++    preceded by a single space, with blank lines in
++    between, but conventions vary here
+ ----
+ 
+-If all your commit messages follow this model, things will be much easier for you and the developers with whom you collaborate.
+-The Git project has well-formatted commit messages -- try running `git log --no-merges` there to see what a nicely-formatted project-commit history looks like.
+-
+-[NOTE]
+-.Do as we say, not as we do.
+-====
+-For the sake of brevity, many of the examples in this book don't have nicely-formatted commit messages like this; instead, we simply use the `-m` option to `git commit`.
++If all your commit messages look like this, things will be a lot easier for you and the developers you work with.
++The Git project has well-formatted commit messages – try running `git log --no-merges` there to see what a nicely formatted project-commit history looks like.
+ 
+-In short, do as we say, not as we do.
+-====
++In the following examples, and throughout most of this book, for the sake of brevity this book doesn't have nicely-formatted messages like this; instead, we use the `-m` option to `git commit`.
++Do as we say, not as we do.
+ 
+-[[_private_team]]
+ ==== Private Small Team
+ 
+-(((contributing, private small team)))
+ The simplest setup you're likely to encounter is a private project with one or two other developers.
+-``Private,'' in this context, means closed-source -- not accessible to the outside world.
++``Private,'' in this context, means closed-source – not accessible to the outside world.
+ You and the other developers all have push access to the repository.
+ 
+ In this environment, you can follow a workflow similar to what you might do when using Subversion or another centralized system.
+ You still get the advantages of things like offline committing and vastly simpler branching and merging, but the workflow can be very similar; the main difference is that merges happen client-side rather than on the server at commit time.
+ Let's see what it might look like when two developers start to work together with a shared repository.
+ The first developer, John, clones the repository, makes a change, and commits locally.
+-The protocol messages have been replaced with `...` in these examples to shorten them somewhat.
++(The protocol messages have been replaced with `...` in these examples to shorten them somewhat.)
+ 
+-[source,console]
+ ----
+ # John's Machine
+ $ git clone john@githost:simplegit.git
+@@ -120,14 +105,13 @@
+ ...
+ $ cd simplegit/
+ $ vim lib/simplegit.rb
+-$ git commit -am 'Remove invalid default value'
+-[master 738ee87] Remove invalid default value
++$ git commit -am 'removed invalid default value'
++[master 738ee87] removed invalid default value
+  1 files changed, 1 insertions(+), 1 deletions(-)
+ ----
+ 
+-The second developer, Jessica, does the same thing -- clones the repository and commits a change:
++The second developer, Jessica, does the same thing – clones the repository and commits a change:
+ 
+-[source,console]
+ ----
+ # Jessica's Machine
+ $ git clone jessica@githost:simplegit.git
+@@ -135,14 +119,13 @@
+ ...
+ $ cd simplegit/
+ $ vim TODO
+-$ git commit -am 'Add reset task'
+-[master fbff5bc] Add reset task
++$ git commit -am 'add reset task'
++[master fbff5bc] add reset task
+  1 files changed, 1 insertions(+), 0 deletions(-)
+ ----
+ 
+-Now, Jessica pushes her work to the server, which works just fine:
++Now, Jessica pushes her work up to the server:
+ 
+-[source,console]
+ ----
+ # Jessica's Machine
+ $ git push origin master
+@@ -151,14 +134,8 @@
+    1edee6b..fbff5bc  master -> master
+ ----
+ 
+-The last line of the output above shows a useful return message from the push operation.
+-The basic format is `<oldref>..<newref> fromref -> toref`, where `oldref` means the old reference, `newref` means the new reference, `fromref` is the name of the local reference being pushed, and `toref` is the name of the remote reference being updated.
+-You'll see similar output like this below in the discussions, so having a basic idea of the meaning will help in understanding the various states of the repositories.
+-More details are available in the documentation for https://git-scm.com/docs/git-push[git-push].
+-
+-Continuing with this example, shortly afterwards, John makes some changes, commits them to his local repository, and tries to push them to the same server:
++John tries to push his change up, too:
+ 
+-[source,console]
+ ----
+ # John's Machine
+ $ git push origin master
+@@ -167,65 +144,39 @@
+ error: failed to push some refs to 'john@githost:simplegit.git'
+ ----
+ 
+-In this case, John's push fails because of Jessica's earlier push of _her_ changes.
++John isn't allowed to push because Jessica has pushed in the meantime.
+ This is especially important to understand if you're used to Subversion, because you'll notice that the two developers didn't edit the same file.
+-Although Subversion automatically does such a merge on the server if different files are edited, with Git, you must _first_ merge the commits locally.
+-In other words, John must first fetch Jessica's upstream changes and merge them into his local repository before he will be allowed to push.
+-
+-As a first step, John fetches Jessica's work (this only _fetches_ Jessica's upstream work, it does not yet merge it into John's work):
+-
+-[source,console]
+-----
+-$ git fetch origin
+-...
+-From john@githost:simplegit
+- + 049d078...fbff5bc master     -> origin/master
+-----
++Although Subversion automatically does such a merge on the server if different files are edited, in Git you must merge the commits locally.
++John has to fetch Jessica's changes and merge them in before he will be allowed to push:
+ 
+ At this point, John's local repository looks something like this:
+ 
+-.John's divergent history
+-image::images/small-team-1.png[John's divergent history]
+-
+-Now John can merge Jessica's work that he fetched into his own local work:
+-
+-[source,console]
+-----
+-$ git merge origin/master
+-Merge made by the 'recursive' strategy.
+- TODO |    1 +
+- 1 files changed, 1 insertions(+), 0 deletions(-)
+-----
++.John's divergent history.
++image::images/small-team-1.png[John's divergent history.]
+ 
+-As long as that local merge goes smoothly, John's updated history will now look like this:
++John has a reference to the changes Jessica pushed up, but he has to merge them into his own work before he is allowed to push:
+ 
+-.John's repository after merging `origin/master`
+-image::images/small-team-2.png[John's repository after merging `origin/master`]
++The merge goes smoothly – John's commit history now looks like this:
+ 
+-At this point, John might want to test this new code to make sure none of Jessica's work affects any of his and, as long as everything seems fine, he can finally push the new merged work up to the server:
++.John's repository after merging `origin/master`.
++image::images/small-team-2.png[John's repository after merging `origin/master`.]
+ 
+-[source,console]
+-----
+-$ git push origin master
+-...
+-To john@githost:simplegit.git
+-   fbff5bc..72bbc59  master -> master
+-----
++Now, John can test his code to make sure it still works properly, and then he can push his new merged work up to the server:
+ 
+-In the end, John's commit history will look like this:
++Finally, John's commit history looks like this:
+ 
+-.John's history after pushing to the `origin` server
+-image::images/small-team-3.png[John's history after pushing to the `origin` server]
++.John's history after pushing to the `origin` server.
++image::images/small-team-3.png[John's history after pushing to the `origin` server.]
+ 
+-In the meantime, Jessica has created a new topic branch called `issue54`, and made three commits to that branch.
++In the meantime, Jessica has been working on a topic branch.
++She's created a topic branch called `issue54` and done three commits on that branch.
+ She hasn't fetched John's changes yet, so her commit history looks like this:
+ 
+-.Jessica's topic branch
+-image::images/small-team-4.png[Jessica's topic branch]
++.Jessica's topic branch.
++image::images/small-team-4.png[Jessica's topic branch.]
+ 
+-Suddenly, Jessica learns that John has pushed some new work to the server and she wants to take a look at it, so she can fetch all new content from the server that she does not yet have with:
++Jessica wants to sync up with John, so she fetches:
+ 
+-[source,console]
+ ----
+ # Jessica's Machine
+ $ git fetch origin
+@@ -237,100 +188,54 @@
+ That pulls down the work John has pushed up in the meantime.
+ Jessica's history now looks like this:
+ 
+-.Jessica's history after fetching John's changes
+-image::images/small-team-5.png[Jessica's history after fetching John's changes]
++.Jessica's history after fetching John's changes.
++image::images/small-team-5.png[Jessica's history after fetching John's changes.]
+ 
+-Jessica thinks her topic branch is ready, but she wants to know what part of John's fetched work she has to merge into her work so that she can push.
++Jessica thinks her topic branch is ready, but she wants to know what she has to merge into her work so that she can push.
+ She runs `git log` to find out:
+ 
+-[source,console]
+-----
+-$ git log --no-merges issue54..origin/master
+-commit 738ee872852dfaa9d6634e0dea7a324040193016
+-Author: John Smith <[e-mail]>
+-Date:   Fri May 29 16:01:27 2009 -0700
+-
+-   Remove invalid default value
+-----
+-
+-The `issue54..origin/master` syntax is a log filter that asks Git to display only those commits that are on the latter branch (in this case `origin/master`) that are not on the first branch (in this case `issue54`).
+-We'll go over this syntax in detail in <<ch07-git-tools#_commit_ranges>>.
++The `issue54..origin/master` syntax is a log filter that asks Git to only show the list of commits that are on the latter branch (in this case `origin/master`) that are not on the first branch (in this case `issue54`).
++We'll go over this syntax in detail in <<ch07-git-tools#r_commit_ranges>>.
+ 
+-From the above output, we can see that there is a single commit that John has made that Jessica has not merged into her local work.
++For now, we can see from the output that there is a single commit that John has made that Jessica has not merged in.
+ If she merges `origin/master`, that is the single commit that will modify her local work.
+ 
+-Now, Jessica can merge her topic work into her `master` branch, merge John's work (`origin/master`) into her `master` branch, and then push back to the server again.
+-
+-First (having committed all of the work on her `issue54` topic branch), Jessica switches back to her `master` branch in preparation for integrating all this work:
+-
+-[source,console]
+-----
+-$ git checkout master
+-Switched to branch 'master'
+-Your branch is behind 'origin/master' by 2 commits, and can be fast-forwarded.
+-----
+-
+-Jessica can merge either `origin/master` or `issue54` first -- they're both upstream, so the order doesn't matter.
+-The end snapshot should be identical no matter which order she chooses; only the history will be different.
+-She chooses to merge the `issue54` branch  first:
+-
+-[source,console]
+-----
+-$ git merge issue54
+-Updating fbff5bc..4af4298
+-Fast forward
+- README           |    1 +
+- lib/simplegit.rb |    6 +++++-
+- 2 files changed, 6 insertions(+), 1 deletions(-)
+-----
+-
+-No problems occur; as you can see it was a simple fast-forward merge.
+-Jessica now completes the local merging process by merging John's earlier fetched work that is sitting in the `origin/master` branch:
++Now, Jessica can merge her topic work into her master branch, merge John's work (`origin/master`) into her `master` branch, and then push back to the server again.
++First, she switches back to her master branch to integrate all this work:
+ 
+-[source,console]
+-----
+-$ git merge origin/master
+-Auto-merging lib/simplegit.rb
+-Merge made by the 'recursive' strategy.
+- lib/simplegit.rb |    2 +-
+- 1 files changed, 1 insertions(+), 1 deletions(-)
+-----
++She can merge either `origin/master` or `issue54` first – they're both upstream, so the order doesn't matter.
++The end snapshot should be identical no matter which order she chooses; only the history will be slightly different.
++She chooses to merge in `issue54` first:
+ 
+-Everything merges cleanly, and Jessica's history now looks like this:
++No problems occur; as you can see it was a simple fast-forward.
++Now Jessica merges in John's work (`origin/master`):
+ 
+-.Jessica's history after merging John's changes
+-image::images/small-team-6.png[Jessica's history after merging John's changes]
++Everything merges cleanly, and Jessica's history looks like this:
+ 
+-Now `origin/master` is reachable from Jessica's `master` branch, so she should be able to successfully push (assuming John hasn't pushed even more changes in the meantime):
++.Jessica's history after merging John's changes.
++image::images/small-team-6.png[Jessica's history after merging John's changes.]
+ 
+-[source,console]
+-----
+-$ git push origin master
+-...
+-To jessica@githost:simplegit.git
+-   72bbc59..8059c15  master -> master
+-----
++Now `origin/master` is reachable from Jessica's `master` branch, so she should be able to successfully push (assuming John hasn't pushed again in the meantime):
+ 
+ Each developer has committed a few times and merged each other's work successfully.
+ 
+-.Jessica's history after pushing all changes back to the server
+-image::images/small-team-7.png[Jessica's history after pushing all changes back to the server]
++.Jessica's history after pushing all changes back to the server.
++image::images/small-team-7.png[Jessica's history after pushing all changes back to the server.]
+ 
+ That is one of the simplest workflows.
+-You work for a while (generally in a topic branch), and merge that work into your `master` branch when it's ready to be integrated.
+-When you want to share that work, you fetch and merge your `master` from `origin/master` if it has changed, and finally push to the `master` branch on the server.
++You work for a while, generally in a topic branch, and merge into your master branch when it's ready to be integrated.
++When you want to share that work, you merge it into your own master branch, then fetch and merge `origin/master` if it has changed, and finally push to the `master` branch on the server.
+ The general sequence is something like this:
+ 
+-.General sequence of events for a simple multiple-developer Git workflow
+-image::images/small-team-flow.png[General sequence of events for a simple multiple-developer Git workflow]
++.General sequence of events for a simple multiple-developer Git workflow.
++image::images/small-team-flow.png[General sequence of events for a simple multiple-developer Git workflow.]
+ 
+ ==== Private Managed Team
+ 
+-(((contributing, private managed team)))
+ In this next scenario, you'll look at contributor roles in a larger private group.
+-You'll learn how to work in an environment where small groups collaborate on features, after which those team-based contributions are integrated by another party.
++You'll learn how to work in an environment where small groups collaborate on features and then those team-based contributions are integrated by another party.
+ 
+-Let's say that John and Jessica are working together on one feature (call this ``featureA''), while Jessica and a third developer, Josie, are working on a second (say, ``featureB'').
++Let's say that John and Jessica are working together on one feature, while Jessica and Josie are working on a second.
+ In this case, the company is using a type of integration-manager workflow where the work of the individual groups is integrated only by certain engineers, and the `master` branch of the main repo can be updated only by those engineers.
+ In this scenario, all work is done in team-based branches and pulled together by the integrators later.
+ 
+@@ -338,33 +243,23 @@
+ Assuming she already has her repository cloned, she decides to work on `featureA` first.
+ She creates a new branch for the feature and does some work on it there:
+ 
+-[source,console]
+ ----
+ # Jessica's Machine
+ $ git checkout -b featureA
+ Switched to a new branch 'featureA'
+ $ vim lib/simplegit.rb
+-$ git commit -am 'Add limit to log function'
+-[featureA 3300904] Add limit to log function
++$ git commit -am 'add limit to log function'
++[featureA 3300904] add limit to log function
+  1 files changed, 1 insertions(+), 1 deletions(-)
+ ----
+ 
+ At this point, she needs to share her work with John, so she pushes her `featureA` branch commits up to the server.
+-Jessica doesn't have push access to the `master` branch -- only the integrators do -- so she has to push to another branch in order to collaborate with John:
+-
+-[source,console]
+-----
+-$ git push -u origin featureA
+-...
+-To jessica@githost:simplegit.git
+- * [new branch]      featureA -> featureA
+-----
++Jessica doesn't have push access to the `master` branch – only the integrators do – so she has to push to another branch in order to collaborate with John:
+ 
+ Jessica emails John to tell him that she's pushed some work into a branch named `featureA` and he can look at it now.
+ While she waits for feedback from John, Jessica decides to start working on `featureB` with Josie.
+ To begin, she starts a new feature branch, basing it off the server's `master` branch:
+ 
+-[source,console]
+ ----
+ # Jessica's Machine
+ $ git fetch origin
+@@ -374,254 +269,120 @@
+ 
+ Now, Jessica makes a couple of commits on the `featureB` branch:
+ 
+-[source,console]
+-----
+-$ vim lib/simplegit.rb
+-$ git commit -am 'Make ls-tree function recursive'
+-[featureB e5b0fdc] Make ls-tree function recursive
+- 1 files changed, 1 insertions(+), 1 deletions(-)
+-$ vim lib/simplegit.rb
+-$ git commit -am 'Add ls-files'
+-[featureB 8512791] Add ls-files
+- 1 files changed, 5 insertions(+), 0 deletions(-)
+-----
+-
+-Jessica's repository now looks like this:
+-
+-.Jessica's initial commit history
+-image::images/managed-team-1.png[Jessica's initial commit history]
+-
+-She's ready to push her work, but gets an email from Josie that a branch with some initial ``featureB'' work on it was already pushed to the server as the `featureBee` branch.
+-Jessica needs to merge those changes with her own before she can push her work to the server.
+-Jessica first fetches Josie's changes with `git fetch`:
+-
+-[source,console]
+-----
+-$ git fetch origin
+-...
+-From jessica@githost:simplegit
+- * [new branch]      featureBee -> origin/featureBee
+-----
++Jessica's repository looks like this:
+ 
+-Assuming Jessica is still on her checked-out `featureB` branch, she can now merge Josie's work into that branch with `git merge`:
++.Jessica's initial commit history.
++image::images/managed-team-1.png[Jessica's initial commit history.]
+ 
+-[source,console]
+-----
+-$ git merge origin/featureBee
+-Auto-merging lib/simplegit.rb
+-Merge made by the 'recursive' strategy.
+- lib/simplegit.rb |    4 ++++
+- 1 files changed, 4 insertions(+), 0 deletions(-)
+-----
++She's ready to push up her work, but gets an email from Josie that a branch with some initial work on it was already pushed to the server as `featureBee`.
++Jessica first needs to merge those changes in with her own before she can push to the server.
++She can then fetch Josie's changes down with `git fetch`:
+ 
+-At this point, Jessica wants to push all of this merged ``featureB'' work back to the server, but she doesn't want to simply push her own `featureB` branch.
+-Rather, since Josie has already started an upstream `featureBee` branch, Jessica wants to push to _that_ branch, which she does with:
++Jessica can now merge this into the work she did with `git merge`:
+ 
+-[source,console]
+-----
+-$ git push -u origin featureB:featureBee
+-...
+-To jessica@githost:simplegit.git
+-   fba9af8..cd685d1  featureB -> featureBee
+-----
++There is a bit of a problem – she needs to push the merged work in her `featureB` branch to the `featureBee` branch on the server.
++She can do so by specifying the local branch followed by a colon (:) followed by the remote branch to the `git push` command:
+ 
+ This is called a _refspec_.
+-See <<ch10-git-internals#_refspec>> for a more detailed discussion of Git refspecs and different things you can do with them.
++See <<ch10-git-internals#r_refspec>> for a more detailed discussion of Git refspecs and different things you can do with them.
+ Also notice the `-u` flag; this is short for `--set-upstream`, which configures the branches for easier pushing and pulling later.
+ 
+-Suddenly, Jessica gets email from John, who tells her he's pushed some changes to the `featureA` branch on which they are collaborating, and he asks Jessica to take a look at them.
+-Again, Jessica runs a simple `git fetch` to fetch _all_ new content from the server, including (of course) John's latest work:
++Next, John emails Jessica to say he's pushed some changes to the `featureA` branch and asks her to verify them.
++She runs a `git fetch` to pull down those changes:
+ 
+-[source,console]
+-----
+-$ git fetch origin
+-...
+-From jessica@githost:simplegit
+-   3300904..aad881d  featureA   -> origin/featureA
+-----
+-
+-Jessica can display the log of John's new work by comparing the content of the newly-fetched `featureA` branch with her local copy of the same branch:
+-
+-[source,console]
+-----
+-$ git log featureA..origin/featureA
+-commit aad881d154acdaeb2b6b18ea0e827ed8a6d671e6
+-Author: John Smith <[e-mail]>
+-Date:   Fri May 29 19:57:33 2009 -0700
+-
+-    Increase log output to 30 from 25
+-----
+-
+-If Jessica likes what she sees, she can merge John's new work into her local `featureA` branch with:
+-
+-[source,console]
+-----
+-$ git checkout featureA
+-Switched to branch 'featureA'
+-$ git merge origin/featureA
+-Updating 3300904..aad881d
+-Fast forward
+- lib/simplegit.rb |   10 +++++++++-
+-1 files changed, 9 insertions(+), 1 deletions(-)
+-----
++Then, she can see what has been changed with `git log`:
+ 
+-Finally, Jessica might want to make a couple minor changes to all that merged content, so she is free to make those changes, commit them to her local `featureA` branch, and push the end result back to the server:
++Finally, she merges John's work into her own `featureA` branch:
+ 
+-[source,console]
+-----
+-$ git commit -am 'Add small tweak to merged content'
+-[featureA 774b3ed] Add small tweak to merged content
+- 1 files changed, 1 insertions(+), 1 deletions(-)
+-$ git push
+-...
+-To jessica@githost:simplegit.git
+-   3300904..774b3ed  featureA -> featureA
+-----
++Jessica wants to tweak something, so she commits again and then pushes this back up to the server:
+ 
+ Jessica's commit history now looks something like this:
+ 
+-.Jessica's history after committing on a feature branch
+-image::images/managed-team-2.png[Jessica's history after committing on a feature branch]
++.Jessica's history after committing on a feature branch.
++image::images/managed-team-2.png[Jessica's history after committing on a feature branch.]
+ 
+-At some point, Jessica, Josie, and John inform the integrators that the `featureA` and `featureBee` branches on the server are ready for integration into the mainline.
++Jessica, Josie, and John inform the integrators that the `featureA` and `featureBee` branches on the server are ready for integration into the mainline.
+ After the integrators merge these branches into the mainline, a fetch will bring down the new merge commit, making the history look like this:
+ 
+-.Jessica's history after merging both her topic branches
+-image::images/managed-team-3.png[Jessica's history after merging both her topic branches]
++.Jessica's history after merging both her topic branches.
++image::images/managed-team-3.png[Jessica's history after merging both her topic branches.]
+ 
+ Many groups switch to Git because of this ability to have multiple teams working in parallel, merging the different lines of work late in the process.
+ The ability of smaller subgroups of a team to collaborate via remote branches without necessarily having to involve or impede the entire team is a huge benefit of Git.
+ The sequence for the workflow you saw here is something like this:
+ 
+-.Basic sequence of this managed-team workflow
+-image::images/managed-team-flow.png[Basic sequence of this managed-team workflow]
++.Basic sequence of this managed-team workflow.
++image::images/managed-team-flow.png[Basic sequence of this managed-team workflow.]
+ 
+-[[_public_project]]
+ ==== Forked Public Project
+ 
+-(((contributing, public small project)))
+ Contributing to public projects is a bit different.
+ Because you don't have the permissions to directly update branches on the project, you have to get the work to the maintainers some other way.
+ This first example describes contributing via forking on Git hosts that support easy forking.
+-Many hosting sites support this (including GitHub, BitBucket, repo.or.cz, and others), and many project maintainers expect this style of contribution.
++Many hosting sites support this (including GitHub, BitBucket, Google Code, repo.or.cz, and others), and many project maintainers expect this style of contribution.
+ The next section deals with projects that prefer to accept contributed patches via email.
+ 
+ First, you'll probably want to clone the main repository, create a topic branch for the patch or patch series you're planning to contribute, and do your work there.
+ The sequence looks basically like this:
+ 
+-[source,console]
+-----
+-$ git clone <url>
+-$ cd project
+-$ git checkout -b featureA
+-  ... work ...
+-$ git commit
+-  ... work ...
+-$ git commit
+-----
+-
+-[NOTE]
+ ====
+-You may want to use `rebase -i` to squash your work down to a single commit, or rearrange the work in the commits to make the patch easier for the maintainer to review -- see <<ch07-git-tools#_rewriting_history>> for more information about interactive rebasing.
++You may want to use `rebase -i` to squash your work down to a single commit, or rearrange the work in the commits to make the patch easier for the maintainer to review – see <<ch07-git-tools#r_rewriting_history>> for more information about interactive rebasing.
+ ====
+ 
+ When your branch work is finished and you're ready to contribute it back to the maintainers, go to the original project page and click the ``Fork'' button, creating your own writable fork of the project.
+-You then need to add this repository URL as a new remote of your local repository; in this example, let's call it `myfork`:
+-
+-[source,console]
+-----
+-$ git remote add myfork <url>
+-----
+-
+-You then need to push your new work to this repository.
+-It's easiest to push the topic branch you're working on to your forked repository, rather than merging that work into your `master` branch and pushing that.
+-The reason is that if your work isn't accepted or is cherry-picked, you don't have to rewind your `master` branch (the Git `cherry-pick` operation is covered in more detail in <<ch05-distributed-git#_rebase_cherry_pick>>).
+-If the maintainers `merge`, `rebase`, or `cherry-pick` your work, you'll eventually get it back via pulling from their repository anyhow.
+-
+-In any event, you can push your work with:
++You then need to add in this new repository URL as a second remote, in this case named `myfork`:
+ 
+-[source,console]
+-----
+-$ git push -u myfork featureA
+-----
+-
+-(((git commands, request-pull)))
+-Once your work has been pushed to your fork of the repository, you need to notify the maintainers of the original project that you have work you'd like them to merge.
+-This is often called a _pull request_, and you typically generate such a request either via the website -- GitHub has its own ``Pull Request'' mechanism that we'll go over in <<ch06-github#ch06-github>> -- or you can run the `git request-pull` command and email the subsequent output to the project maintainer manually.
+-
+-The `git request-pull` command takes the base branch into which you want your topic branch pulled and the Git repository URL you want them to pull from, and produces a summary of all the changes you're asking to be pulled.
+-For instance, if Jessica wants to send John a pull request, and she's done two commits on the topic branch she just pushed, she can run this:
+-
+-[source,console]
+-----
+-$ git request-pull origin/master myfork
+-The following changes since commit 1edee6b1d61823a2de3b09c160d7080b8d1b3a40:
+-Jessica Smith (1):
+-        Create new function
++Then you need to push your work up to it.
++It's easiest to push the topic branch you're working on up to your repository, rather than merging into your master branch and pushing that up.
++The reason is that if the work isn't accepted or is cherry picked, you don't have to rewind your master branch.
++If the maintainers merge, rebase, or cherry-pick your work, you'll eventually get it back via pulling from their repository anyhow:
+ 
+-are available in the git repository at:
++When your work has been pushed up to your fork, you need to notify the maintainer.
++This is often called a pull request, and you can either generate it via the website – GitHub has its own Pull Request mechanism that we'll go over in <<ch06-github#ch06-github>> – or you can run the `git request-pull` command and email the output to the project maintainer manually.
+ 
+-  git://githost/simplegit.git featureA
++The `request-pull` command takes the base branch into which you want your topic branch pulled and the Git repository URL you want them to pull from, and outputs a summary of all the changes you're asking to be pulled in.
++For instance, if Jessica wants to send John a pull request, and she's done two commits on the topic branch she just pushed up, she can run this:
+ 
+-Jessica Smith (2):
+-      Add limit to log function
+-      Increase log output to 30 from 25
+-
+- lib/simplegit.rb |   10 +++++++++-
+- 1 files changed, 9 insertions(+), 1 deletions(-)
+-----
+-
+-This output can be sent to the maintainer -- it tells them where the work was branched from, summarizes the commits, and identifies from where the new work is to be pulled.
++The output can be sent to the maintainer – it tells them where the work was branched from, summarizes the commits, and tells where to pull this work from.
+ 
+ On a project for which you're not the maintainer, it's generally easier to have a branch like `master` always track `origin/master` and to do your work in topic branches that you can easily discard if they're rejected.
+ Having work themes isolated into topic branches also makes it easier for you to rebase your work if the tip of the main repository has moved in the meantime and your commits no longer apply cleanly.
+-For example, if you want to submit a second topic of work to the project, don't continue working on the topic branch you just pushed up -- start over from the main repository's `master` branch:
++For example, if you want to submit a second topic of work to the project, don't continue working on the topic branch you just pushed up – start over from the main repository's `master` branch:
+ 
+ [source,console]
+ ----
+ $ git checkout -b featureB origin/master
+-  ... work ...
++# (work)
+ $ git commit
+ $ git push myfork featureB
+-$ git request-pull origin/master myfork
+-  ... email generated request pull to maintainer ...
++# (email maintainer)
+ $ git fetch origin
+ ----
+ 
+-Now, each of your topics is contained within a silo -- similar to a patch queue -- that you can rewrite, rebase, and modify without the topics interfering or interdepending on each other, like so:
++Now, each of your topics is contained within a silo – similar to a patch queue – that you can rewrite, rebase, and modify without the topics interfering or interdepending on each other, like so:
+ 
+-.Initial commit history with `featureB` work
+-image::images/public-small-1.png[Initial commit history with `featureB` work]
++.Initial commit history with `featureB` work.
++image::images/public-small-1.png[Initial commit history with `featureB` work.]
+ 
+ Let's say the project maintainer has pulled in a bunch of other patches and tried your first branch, but it no longer cleanly merges.
+ In this case, you can try to rebase that branch on top of `origin/master`, resolve the conflicts for the maintainer, and then resubmit your changes:
+ 
+-[source,console]
+-----
+-$ git checkout featureA
+-$ git rebase origin/master
+-$ git push -f myfork featureA
+-----
++This rewrites your history to now look like <<rpsp_b>>.
+ 
+-This rewrites your history to now look like <<psp_b>>.
+-
+-[[psp_b]]
+-.Commit history after `featureA` work
+-image::images/public-small-2.png[Commit history after `featureA` work]
++.Commit history after `featureA` work.
++image::images/public-small-2.png[Commit history after `featureA` work.]
+ 
+ Because you rebased the branch, you have to specify the `-f` to your push command in order to be able to replace the `featureA` branch on the server with a commit that isn't a descendant of it.
+ An alternative would be to push this new work to a different branch on the server (perhaps called `featureAv2`).
+ 
+ Let's look at one more possible scenario: the maintainer has looked at work in your second branch and likes the concept but would like you to change an implementation detail.
+ You'll also take this opportunity to move the work to be based off the project's current `master` branch.
+-You start a new branch based off the current `origin/master` branch, squash the `featureB` changes there, resolve any conflicts, make the implementation change, and then push that as a new branch:
++You start a new branch based off the current `origin/master` branch, squash the `featureB` changes there, resolve any conflicts, make the implementation change, and then push that up as a new branch:
+ 
+-(((git commands, merge, squash)))
+-[source,console]
+ ----
+ $ git checkout -b featureBv2 origin/master
+ $ git merge --squash featureB
+-  ... change implementation ...
++# (change implementation)
+ $ git commit
+ $ git push myfork featureBv2
+ ----
+@@ -630,173 +391,61 @@
+ This means your future commit will have one parent only and allows you to introduce all the changes from another branch and then make more changes before recording the new commit.
+ Also the `--no-commit` option can be useful to delay the merge commit in case of the default merge process.
+ 
+-At this point, you can notify the maintainer that you've made the requested changes, and that they can find those changes in your `featureBv2` branch.
++Now you can send the maintainer a message that you've made the requested changes and they can find those changes in your `featureBv2` branch.
+ 
+-.Commit history after `featureBv2` work
+-image::images/public-small-3.png[Commit history after `featureBv2` work]
++.Commit history after `featureBv2` work.
++image::images/public-small-3.png[Commit history after `featureBv2` work.]
+ 
+-[[_project_over_email]]
+ ==== Public Project over Email
+ 
+-(((contributing, public large project)))
+-Many projects have established procedures for accepting patches -- you'll need to check the specific rules for each project, because they will differ.
++Many projects have established procedures for accepting patches – you'll need to check the specific rules for each project, because they will differ.
+ Since there are several older, larger projects which accept patches via a developer mailing list, we'll go over an example of that now.
+ 
+-The workflow is similar to the previous use case -- you create topic branches for each patch series you work on.
++The workflow is similar to the previous use case – you create topic branches for each patch series you work on.
+ The difference is how you submit them to the project.
+ Instead of forking the project and pushing to your own writable version, you generate email versions of each commit series and email them to the developer mailing list:
+ 
+-[source,console]
+ ----
+ $ git checkout -b topicA
+-  ... work ...
++# (work)
+ $ git commit
+-  ... work ...
++# (work)
+ $ git commit
+ ----
+ 
+-(((git commands, format-patch)))
+ Now you have two commits that you want to send to the mailing list.
+-You use `git format-patch` to generate the mbox-formatted files that you can email to the list -- it turns each commit into an email message with the first line of the commit message as the subject and the rest of the message plus the patch that the commit introduces as the body.
++You use `git format-patch` to generate the mbox-formatted files that you can email to the list – it turns each commit into an email message with the first line of the commit message as the subject and the rest of the message plus the patch that the commit introduces as the body.
+ The nice thing about this is that applying a patch from an email generated with `format-patch` preserves all the commit information properly.
+ 
+-[source,console]
+-----
+-$ git format-patch -M origin/master
+-0001-add-limit-to-log-function.patch
+-0002-increase-log-output-to-30-from-25.patch
+-----
+-
+ The `format-patch` command prints out the names of the patch files it creates.
+ The `-M` switch tells Git to look for renames.
+ The files end up looking like this:
+ 
+-[source,console]
+-----
+-$ cat 0001-add-limit-to-log-function.patch
+-From 330090432754092d704da8e76ca5c05c198e71a8 Mon Sep 17 00:00:00 2001
+-From: Jessica Smith <[e-mail]>
+-Date: Sun, 6 Apr 2008 10:17:23 -0700
+-Subject: [PATCH 1/2] Add limit to log function
+-
+-Limit log functionality to the first 20
+-
+----
+- lib/simplegit.rb |    2 +-
+- 1 files changed, 1 insertions(+), 1 deletions(-)
+-
+-diff --git a/lib/simplegit.rb b/lib/simplegit.rb
+-index 76f47bc..f9815f1 100644
+---- a/lib/simplegit.rb
+-+++ b/lib/simplegit.rb
+-@@ -14,7 +14,7 @@ class SimpleGit
+-   end
+-
+-   def log(treeish = 'master')
+--    command("git log #{treeish}")
+-+    command("git log -n 20 #{treeish}")
+-   end
+-
+-   def ls_tree(treeish = 'master')
+---
+-2.1.0
+-----
+-
+ You can also edit these patch files to add more information for the email list that you don't want to show up in the commit message.
+-If you add text between the `---` line and the beginning of the patch (the `diff --git` line), the developers can read it, but that content is ignored by the patching process.
++If you add text between the `---` line and the beginning of the patch (the `diff --git` line), then developers can read it; but applying the patch excludes it.
+ 
+ To email this to a mailing list, you can either paste the file into your email program or send it via a command-line program.
+ Pasting the text often causes formatting issues, especially with ``smarter'' clients that don't preserve newlines and other whitespace appropriately.
+ Luckily, Git provides a tool to help you send properly formatted patches via IMAP, which may be easier for you.
+ We'll demonstrate how to send a patch via Gmail, which happens to be the email agent we know best; you can read detailed instructions for a number of mail programs at the end of the aforementioned `Documentation/SubmittingPatches` file in the Git source code.
+ 
+-(((git commands, config)))(((email)))
+ First, you need to set up the imap section in your `~/.gitconfig` file.
+ You can set each value separately with a series of `git config` commands, or you can add them manually, but in the end your config file should look something like this:
+ 
+-[source,ini]
+-----
+-[imap]
+-  folder = "[Gmail]/Drafts"
+-  host = imaps://imap.gmail.com
+-  user = [e-mail]
+-  pass = YX]8g76G_2^sFbd
+-  port = 993
+-  sslverify = false
+-----
+-
+ If your IMAP server doesn't use SSL, the last two lines probably aren't necessary, and the host value will be `imap://` instead of `imaps://`.
+ When that is set up, you can use `git imap-send` to place the patch series in the Drafts folder of the specified IMAP server:
+ 
+-[source,console]
+-----
+-$ cat *.patch |git imap-send
+-Resolving imap.gmail.com... ok
+-Connecting to [74.125.142.109]:993... ok
+-Logging in...
+-sending 2 messages
+-100% (2/2) done
+-----
+-
+ At this point, you should be able to go to your Drafts folder, change the To field to the mailing list you're sending the patch to, possibly CC the maintainer or person responsible for that section, and send it off.
+ 
+ You can also send the patches through an SMTP server.
+ As before, you can set each value separately with a series of `git config` commands, or you can add them manually in the sendemail section in your `~/.gitconfig` file:
+ 
+-[source,ini]
+-----
+-[sendemail]
+-  smtpencryption = tls
+-  smtpserver = smtp.gmail.com
+-  smtpuser = [e-mail]
+-  smtpserverport = 587
+-----
+-
+ After this is done, you can use `git send-email` to send your patches:
+ 
+-[source,console]
+-----
+-$ git send-email *.patch
+-0001-add-limit-to-log-function.patch
+-0002-increase-log-output-to-30-from-25.patch
+-Who should the emails appear to be from? [Jessica Smith <[e-mail]>]
+-Emails will be sent from: Jessica Smith <[e-mail]>
+-Who should the emails be sent to? [e-mail]
+-Message-ID to be used as In-Reply-To for the first email? y
+-----
+-
+ Then, Git spits out a bunch of log information looking something like this for each patch you're sending:
+ 
+-[source,text]
+-----
+-(mbox) Adding cc: Jessica Smith <[e-mail]> from
+-  \line 'From: Jessica Smith <[e-mail]>'
+-OK. Log says:
+-Sendmail: /usr/sbin/sendmail -i [e-mail]
+-From: Jessica Smith <[e-mail]>
+-To: [e-mail]
+-Subject: [PATCH 1/2] Add limit to log function
+-Date: Sat, 30 May 2009 13:29:15 -0700
+-Message-Id: <[e-mail]>
+-X-Mailer: git-send-email 1.6.2.rc1.20.g8c5b.dirty
+-In-Reply-To: <y>
+-References: <y>
+-
+-Result: OK
+-----
+-
+-[TIP]
+-====
+-For help on configuring your system and email, more tips and tricks, and a sandbox to send a trial patch via email, go to [git-send-email.io](https://git-send-email.io/).
+-====
+-
+ ==== Summary
+ 
+-In this section, we covered multiple workflows, and talked about the differences between working as part of a small team on closed-source projects vs contributing to a big public project.
+-You know to check for white-space errors before committing, and can write a great commit message.
+-You learned how to format patches, and e-mail them to a developer mailing list.
+-Dealing with merges was also covered in the context of the different workflows.
+-You are now well prepared to collaborate on any project.
+-
++This section has covered a number of common workflows for dealing with several very different types of Git projects you're likely to encounter, and introduced a couple of new tools to help you manage this process.
+ Next, you'll see how to work the other side of the coin: maintaining a Git project.
+ You'll learn how to be a benevolent dictator or integration manager.
+diff -au ../../git/progit2/progit2/book/05-distributed-git/sections/distributed-workflows.asc /tmp/book/05-distributed-git/sections/distributed-workflows.asc.tmp
+--- ../../git/progit2/progit2/book/05-distributed-git/sections/distributed-workflows.asc	2020-07-04 16:36:46.728685513 +0900
++++ /tmp/book/05-distributed-git/sections/distributed-workflows.asc.tmp	2020-10-25 09:24:25.747971004 +0900
+@@ -1,21 +1,19 @@
+ === Distributed Workflows
+ 
+-(((workflows)))
+-In contrast with Centralized Version Control Systems (CVCSs), the distributed nature of Git allows you to be far more flexible in how developers collaborate on projects.
+-In centralized systems, every developer is a node working more or less equally with a central hub.
+-In Git, however, every developer is potentially both a node and a hub; that is, every developer can both contribute code to other repositories and maintain a public repository on which others can base their work and which they can contribute to.
+-This presents a vast range of workflow possibilities for your project and/or your team, so we'll cover a few common paradigms that take advantage of this flexibility.
++Unlike Centralized Version Control Systems (CVCSs), the distributed nature of Git allows you to be far more flexible in how developers collaborate on projects.
++In centralized systems, every developer is a node working more or less equally on a central hub.
++In Git, however, every developer is potentially both a node and a hub – that is, every developer can both contribute code to other repositories and maintain a public repository on which others can base their work and which they can contribute to.
++This opens a vast range of workflow possibilities for your project and/or your team, so we'll cover a few common paradigms that take advantage of this flexibility.
+ We'll go over the strengths and possible weaknesses of each design; you can choose a single one to use, or you can mix and match features from each.
+ 
+ ==== Centralized Workflow
+ 
+-(((workflows, centralized)))
+-In centralized systems, there is generally a single collaboration model -- the centralized workflow.
+-One central hub, or _repository_, can accept code, and everyone synchronizes their work with it.
+-A number of developers are nodes -- consumers of that hub -- and synchronize with that centralized location.
++In centralized systems, there is generally a single collaboration model–the centralized workflow.
++One central hub, or repository, can accept code, and everyone synchronizes their work to it.
++A number of developers are nodes – consumers of that hub – and synchronize to that one place.
+ 
+-.Centralized workflow
+-image::images/centralized_workflow.png[Centralized workflow]
++.Centralized workflow.
++image::images/centralized_workflow.png[Centralized workflow.]
+ 
+ This means that if two developers clone from the hub and both make changes, the first developer to push their changes back up can do so with no problems.
+ The second developer must merge in the first one's work before pushing changes up, so as not to overwrite the first developer's changes.
+@@ -23,7 +21,6 @@
+ 
+ If you are already comfortable with a centralized workflow in your company or team, you can easily continue using that workflow with Git.
+ Simply set up a single repository, and give everyone on your team push access; Git won't let users overwrite each other.
+-
+ Say John and Jessica both start working at the same time.
+ John finishes his change and pushes it to the server.
+ Then Jessica tries to push her changes, but the server rejects them.
+@@ -33,68 +30,50 @@
+ This is also not limited to small teams.
+ With Git's branching model, it's possible for hundreds of developers to successfully work on a single project through dozens of branches simultaneously.
+ 
+-[[_integration_manager]]
+ ==== Integration-Manager Workflow
+ 
+-(((workflows, integration manager)))
+ Because Git allows you to have multiple remote repositories, it's possible to have a workflow where each developer has write access to their own public repository and read access to everyone else's.
+ This scenario often includes a canonical repository that represents the ``official'' project.
+ To contribute to that project, you create your own public clone of the project and push your changes to it.
+ Then, you can send a request to the maintainer of the main project to pull in your changes.
+ The maintainer can then add your repository as a remote, test your changes locally, merge them into their branch, and push back to their repository.
+-The process works as follows (see <<wfdiag_b>>):
++The process works as follows (see <<rwfdiag_b>>):
+ 
+ 1.  The project maintainer pushes to their public repository.
+ 2.  A contributor clones that repository and makes changes.
+ 3.  The contributor pushes to their own public copy.
+ 4.  The contributor sends the maintainer an email asking them to pull changes.
+-5.  The maintainer adds the contributor's repository as a remote and merges locally.
++5.  The maintainer adds the contributor's repo as a remote and merges locally.
+ 6.  The maintainer pushes merged changes to the main repository.
+ 
+-[[wfdiag_b]]
+-.Integration-manager workflow
+-image::images/integration-manager.png[Integration-manager workflow]
++.Integration-manager workflow.
++image::images/integration-manager.png[Integration-manager workflow.]
+ 
+-(((forking)))
+ This is a very common workflow with hub-based tools like GitHub or GitLab, where it's easy to fork a project and push your changes into your fork for everyone to see.
+ One of the main advantages of this approach is that you can continue to work, and the maintainer of the main repository can pull in your changes at any time.
+-Contributors don't have to wait for the project to incorporate their changes -- each party can work at their own pace.
++Contributors don't have to wait for the project to incorporate their changes – each party can work at their own pace.
+ 
+ ==== Dictator and Lieutenants Workflow
+ 
+-(((workflows, dictator and lieutenants)))
+ This is a variant of a multiple-repository workflow.
+ It's generally used by huge projects with hundreds of collaborators; one famous example is the Linux kernel.
+-Various integration managers are in charge of certain parts of the repository; they're called _lieutenants_.
++Various integration managers are in charge of certain parts of the repository; they're called lieutenants.
+ All the lieutenants have one integration manager known as the benevolent dictator.
+-The benevolent dictator pushes from their directory to a reference repository from which all the collaborators need to pull.
+-The process works like this (see <<wfdiag_c>>):
++The benevolent dictator's repository serves as the reference repository from which all the collaborators need to pull.
++The process works like this (see <<rwfdiag_c>>):
+ 
+ 1.  Regular developers work on their topic branch and rebase their work on top of `master`.
+-    The `master` branch is that of the reference repository to which the dictator pushes.
++    The `master` branch is that of the dictator.
+ 2.  Lieutenants merge the developers' topic branches into their `master` branch.
+ 3.  The dictator merges the lieutenants' `master` branches into the dictator's `master` branch.
+-4.  Finally, the dictator pushes that `master` branch to the reference repository so the other developers can rebase on it.
++4.  The dictator pushes their `master` to the reference repository so the other developers can rebase on it.
+ 
+-[[wfdiag_c]]
+-.Benevolent dictator workflow
+-image::images/benevolent-dictator.png[Benevolent dictator workflow]
++.Benevolent dictator workflow.
++image::images/benevolent-dictator.png[Benevolent dictator workflow.]
+ 
+ This kind of workflow isn't common, but can be useful in very big projects, or in highly hierarchical environments.
+ It allows the project leader (the dictator) to delegate much of the work and collect large subsets of code at multiple points before integrating them.
+ 
+-[[_patterns_for_managing_source_code_branches]]
+-==== Patterns for Managing Source Code Branches
+-
+-[NOTE]
+-====
+-Martin Fowler has made a guide "Patterns for Managing Source Code Branches".
+-This guide covers all the common Git workflows, and explains how/when to use them.
+-There's also a section comparing high and low integration frequencies.
+-
+-https://martinfowler.com/articles/branching-patterns.html
+-====
+-
+ ==== Workflows Summary
+ 
+ These are some commonly used workflows that are possible with a distributed system like Git, but you can see that many variations are possible to suit your particular real-world workflow.
+diff -au ../../git/progit2/progit2/book/05-distributed-git/sections/maintaining.asc /tmp/book/05-distributed-git/sections/maintaining.asc.tmp
+--- ../../git/progit2/progit2/book/05-distributed-git/sections/maintaining.asc	2020-07-07 09:30:48.190756402 +0900
++++ /tmp/book/05-distributed-git/sections/maintaining.asc.tmp	2020-10-25 09:24:25.755971381 +0900
+@@ -1,122 +1,64 @@
+ === Maintaining a Project
+ 
+-(((maintaining a project)))
+-In addition to knowing how to contribute effectively to a project, you'll likely need to know how to maintain one.
++In addition to knowing how to effectively contribute to a project, you'll likely need to know how to maintain one.
+ This can consist of accepting and applying patches generated via `format-patch` and emailed to you, or integrating changes in remote branches for repositories you've added as remotes to your project.
+ Whether you maintain a canonical repository or want to help by verifying or approving patches, you need to know how to accept work in a way that is clearest for other contributors and sustainable by you over the long run.
+ 
+ ==== Working in Topic Branches
+ 
+-(((branches, topic)))
+-When you're thinking of integrating new work, it's generally a good idea to try it out in a _topic branch_ -- a temporary branch specifically made to try out that new work.
++When you're thinking of integrating new work, it's generally a good idea to try it out in a topic branch – a temporary branch specifically made to try out that new work.
+ This way, it's easy to tweak a patch individually and leave it if it's not working until you have time to come back to it.
+ If you create a simple branch name based on the theme of the work you're going to try, such as `ruby_client` or something similarly descriptive, you can easily remember it if you have to abandon it for a while and come back later.
+-The maintainer of the Git project tends to namespace these branches as well -- such as `sc/ruby_client`, where `sc` is short for the person who contributed the work.
+-As you'll remember, you can create the branch based off your `master` branch like this:
+-
+-[source,console]
+-----
+-$ git branch sc/ruby_client master
+-----
++The maintainer of the Git project tends to namespace these branches as well – such as `sc/ruby_client`, where `sc` is short for the person who contributed the work.
++As you'll remember, you can create the branch based off your master branch like this:
+ 
+ Or, if you want to also switch to it immediately, you can use the `checkout -b` option:
+ 
+-[source,console]
+-----
+-$ git checkout -b sc/ruby_client master
+-----
+-
+-Now you're ready to add the contributed work that you received into this topic branch and determine if you want to merge it into your longer-term branches.
++Now you're ready to add your contributed work into this topic branch and determine if you want to merge it into your longer-term branches.
+ 
+-[[_patches_from_email]]
+ ==== Applying Patches from Email
+ 
+-(((email, applying patches from)))
+ If you receive a patch over email that you need to integrate into your project, you need to apply the patch in your topic branch to evaluate it.
+ There are two ways to apply an emailed patch: with `git apply` or with `git am`.
+ 
+ ===== Applying a Patch with apply
+ 
+-(((git commands, apply)))
+-If you received the patch from someone who generated it with `git diff` or some variation of the Unix `diff` command (which is not recommended; see the next section), you can apply it with the `git apply` command.
++If you received the patch from someone who generated it with the `git diff` or a Unix `diff` command (which is not recommended; see the next section), you can apply it with the `git apply` command.
+ Assuming you saved the patch at `/tmp/patch-ruby-client.patch`, you can apply the patch like this:
+ 
+-[source,console]
+-----
+-$ git apply /tmp/patch-ruby-client.patch
+-----
+-
+ This modifies the files in your working directory.
+ It's almost identical to running a `patch -p1` command to apply the patch, although it's more paranoid and accepts fewer fuzzy matches than patch.
+ It also handles file adds, deletes, and renames if they're described in the `git diff` format, which `patch` won't do.
+ Finally, `git apply` is an ``apply all or abort all'' model where either everything is applied or nothing is, whereas `patch` can partially apply patchfiles, leaving your working directory in a weird state.
+ `git apply` is overall much more conservative than `patch`.
+-It won't create a commit for you -- after running it, you must stage and commit the changes introduced manually.
++It won't create a commit for you – after running it, you must stage and commit the changes introduced manually.
+ 
+-You can also use `git apply` to see if a patch applies cleanly before you try actually applying it -- you can run `git apply --check` with the patch:
+-
+-[source,console]
+-----
+-$ git apply --check 0001-see-if-this-helps-the-gem.patch
+-error: patch failed: ticgit.gemspec:1
+-error: ticgit.gemspec: patch does not apply
+-----
++You can also use git apply to see if a patch applies cleanly before you try actually applying it – you can run `git apply --check` with the patch:
+ 
+ If there is no output, then the patch should apply cleanly.
+ This command also exits with a non-zero status if the check fails, so you can use it in scripts if you want.
+ 
+-[[_git_am]]
+ ===== Applying a Patch with `am`
+ 
+-(((git commands, am)))
+ If the contributor is a Git user and was good enough to use the `format-patch` command to generate their patch, then your job is easier because the patch contains author information and a commit message for you.
+ If you can, encourage your contributors to use `format-patch` instead of `diff` to generate patches for you.
+ You should only have to use `git apply` for legacy patches and things like that.
+ 
+-To apply a patch generated by `format-patch`, you use `git am` (the command is named `am` as it is used to "apply a series of patches from a mailbox").
++To apply a patch generated by `format-patch`, you use `git am`.
+ Technically, `git am` is built to read an mbox file, which is a simple, plain-text format for storing one or more email messages in one text file.
+ It looks something like this:
+ 
+-[source,console]
+-----
+-From 330090432754092d704da8e76ca5c05c198e71a8 Mon Sep 17 00:00:00 2001
+-From: Jessica Smith <[e-mail]>
+-Date: Sun, 6 Apr 2008 10:17:23 -0700
+-Subject: [PATCH 1/2] Add limit to log function
+-
+-Limit log functionality to the first 20
+-----
++This is the beginning of the output of the format-patch command that you saw in the previous section.
++This is also a valid mbox email format.
++If someone has emailed you the patch properly using git send-email, and you download that into an mbox format, then you can point git am to that mbox file, and it will start applying all the patches it sees.
++If you run a mail client that can save several emails out in mbox format, you can save entire patch series into a file and then use git am to apply them one at a time.
+ 
+-This is the beginning of the output of the `git format-patch` command that you saw in the previous section; it also represents a valid mbox email format.
+-If someone has emailed you the patch properly using `git send-email`, and you download that into an mbox format, then you can point `git am` to that mbox file, and it will start applying all the patches it sees.
+-If you run a mail client that can save several emails out in mbox format, you can save entire patch series into a file and then use `git am` to apply them one at a time.
+-
+-However, if someone uploaded a patch file generated via `git format-patch` to a ticketing system or something similar, you can save the file locally and then pass that file saved on your disk to `git am` to apply it:
+-
+-[source,console]
+-----
+-$ git am 0001-limit-log-function.patch
+-Applying: Add limit to log function
+-----
++However, if someone uploaded a patch file generated via `format-patch` to a ticketing system or something similar, you can save the file locally and then pass that file saved on your disk to `git am` to apply it:
+ 
+ You can see that it applied cleanly and automatically created the new commit for you.
+ The author information is taken from the email's `From` and `Date` headers, and the message of the commit is taken from the `Subject` and body (before the patch) of the email.
+ For example, if this patch was applied from the mbox example above, the commit generated would look something like this:
+ 
+-[source,console]
+-----
+-$ git log --pretty=fuller -1
+-commit 6c5e70b984a60b3cecd395edd5b48a7575bf58e0
+-Author:     Jessica Smith <[e-mail]>
+-AuthorDate: Sun Apr 6 10:17:23 2008 -0700
+-Commit:     Scott Chacon <[e-mail]>
+-CommitDate: Thu Apr 9 09:19:06 2009 -0700
+-
+-   Add limit to log function
+-
+-   Limit log functionality to the first 20
+-----
+-
+ The `Commit` information indicates the person who applied the patch and the time it was applied.
+ The `Author` information is the individual who originally created the patch and when it was originally created.
+ 
+@@ -124,84 +66,41 @@
+ Perhaps your main branch has diverged too far from the branch the patch was built from, or the patch depends on another patch you haven't applied yet.
+ In that case, the `git am` process will fail and ask you what you want to do:
+ 
+-[source,console]
+-----
+-$ git am 0001-see-if-this-helps-the-gem.patch
+-Applying: See if this helps the gem
+-error: patch failed: ticgit.gemspec:1
+-error: ticgit.gemspec: patch does not apply
+-Patch failed at 0001.
+-When you have resolved this problem run "git am --resolved".
+-If you would prefer to skip this patch, instead run "git am --skip".
+-To restore the original branch and stop patching run "git am --abort".
+-----
+-
+ This command puts conflict markers in any files it has issues with, much like a conflicted merge or rebase operation.
+-You solve this issue much the same way -- edit the file to resolve the conflict, stage the new file, and then run `git am --resolved` to continue to the next patch:
++You solve this issue much the same way – edit the file to resolve the conflict, stage the new file, and then run `git am --resolved` to continue to the next patch:
+ 
+-[source,console]
+ ----
+ $ (fix the file)
+ $ git add ticgit.gemspec
+ $ git am --resolved
+-Applying: See if this helps the gem
++Applying: seeing if this helps the gem
+ ----
+ 
+ If you want Git to try a bit more intelligently to resolve the conflict, you can pass a `-3` option to it, which makes Git attempt a three-way merge.
+ This option isn't on by default because it doesn't work if the commit the patch says it was based on isn't in your repository.
+-If you do have that commit -- if the patch was based on a public commit -- then the `-3` option is generally much smarter about applying a conflicting patch:
+-
+-[source,console]
+-----
+-$ git am -3 0001-see-if-this-helps-the-gem.patch
+-Applying: See if this helps the gem
+-error: patch failed: ticgit.gemspec:1
+-error: ticgit.gemspec: patch does not apply
+-Using index info to reconstruct a base tree...
+-Falling back to patching base and 3-way merge...
+-No changes -- Patch already applied.
+-----
++If you do have that commit – if the patch was based on a public commit – then the `-3` option is generally much smarter about applying a conflicting patch:
+ 
+-In this case, without the `-3` option the patch would have been considered as a conflict.
+-Since the `-3` option was used the patch applied cleanly.
++In this case, this patch had already been applied.
++Without the `-3` option, it looks like a conflict.
+ 
+ If you're applying a number of patches from an mbox, you can also run the `am` command in interactive mode, which stops at each patch it finds and asks if you want to apply it:
+ 
+-[source,console]
+-----
+-$ git am -3 -i mbox
+-Commit Body is:
+---------------------------
+-See if this helps the gem
+---------------------------
+-Apply? [y]es/[n]o/[e]dit/[v]iew patch/[a]ccept all
+-----
+-
+ This is nice if you have a number of patches saved, because you can view the patch first if you don't remember what it is, or not apply the patch if you've already done so.
+ 
+ When all the patches for your topic are applied and committed into your branch, you can choose whether and how to integrate them into a longer-running branch.
+ 
+-[[_checking_out_remotes]]
+ ==== Checking Out Remote Branches
+ 
+-(((branches, remote)))
+ If your contribution came from a Git user who set up their own repository, pushed a number of changes into it, and then sent you the URL to the repository and the name of the remote branch the changes are in, you can add them as a remote and do merges locally.
+ 
+ For instance, if Jessica sends you an email saying that she has a great new feature in the `ruby-client` branch of her repository, you can test it by adding the remote and checking out that branch locally:
+ 
+-[source,console]
+-----
+-$ git remote add jessica git://github.com/jessica/myproject.git
+-$ git fetch jessica
+-$ git checkout -b rubyclient jessica/ruby-client
+-----
+-
+-If she emails you again later with another branch containing another great feature, you could directly `fetch` and `checkout` because you already have the remote setup.
++If she emails you again later with another branch containing another great feature, you can fetch and check out because you already have the remote setup.
+ 
+ This is most useful if you're working with a person consistently.
+ If someone only has a single patch to contribute once in a while, then accepting it over email may be less time consuming than requiring everyone to run their own server and having to continually add and remove remotes to get a few patches.
+ You're also unlikely to want to have hundreds of remotes, each for someone who contributes only a patch or two.
+-However, scripts and hosted services may make this easier -- it depends largely on how you develop and how your contributors develop.
++However, scripts and hosted services may make this easier – it depends largely on how you develop and how your contributors develop.
+ 
+ The other advantage of this approach is that you get the history of the commits as well.
+ Although you may have legitimate merge issues, you know where in your history their work is based; a proper three-way merge is the default rather than having to supply a `-3` and hope the patch was generated off a public commit to which you have access.
+@@ -209,53 +108,22 @@
+ If you aren't working with a person consistently but still want to pull from them in this way, you can provide the URL of the remote repository to the `git pull` command.
+ This does a one-time pull and doesn't save the URL as a remote reference:
+ 
+-[source,console]
+-----
+-$ git pull https://github.com/onetimeguy/project
+-From https://github.com/onetimeguy/project
+- * branch            HEAD       -> FETCH_HEAD
+-Merge made by the 'recursive' strategy.
+-----
+-
+-[[_what_is_introduced]]
+ ==== Determining What Is Introduced
+ 
+-(((branches, diffing)))
+ Now you have a topic branch that contains contributed work.
+ At this point, you can determine what you'd like to do with it.
+ This section revisits a couple of commands so you can see how you can use them to review exactly what you'll be introducing if you merge this into your main branch.
+ 
+-It's often helpful to get a review of all the commits that are in this branch but that aren't in your `master` branch.
+-You can exclude commits in the `master` branch by adding the `--not` option before the branch name.
++It's often helpful to get a review of all the commits that are in this branch but that aren't in your master branch.
++You can exclude commits in the master branch by adding the `--not` option before the branch name.
+ This does the same thing as the `master..contrib` format that we used earlier.
+ For example, if your contributor sends you two patches and you create a branch called `contrib` and applied those patches there, you can run this:
+ 
+-[source,console]
+-----
+-$ git log contrib --not master
+-commit 5b6235bd297351589efc4d73316f0a68d484f118
+-Author: Scott Chacon <[e-mail]>
+-Date:   Fri Oct 24 09:53:59 2008 -0700
+-
+-    See if this helps the gem
+-
+-commit 7482e0d16d04bea79d0dba8988cc78df655f16a0
+-Author: Scott Chacon <[e-mail]>
+-Date:   Mon Oct 22 19:38:36 2008 -0700
+-
+-    Update gemspec to hopefully work better
+-----
+-
+ To see what changes each commit introduces, remember that you can pass the `-p` option to `git log` and it will append the diff introduced to each commit.
+ 
+ To see a full diff of what would happen if you were to merge this topic branch with another branch, you may have to use a weird trick to get the correct results.
+ You may think to run this:
+ 
+-[source,console]
+-----
+-$ git diff master
+-----
+-
+ This command gives you a diff, but it may be misleading.
+ If your `master` branch has moved forward since you created the topic branch from it, then you'll get seemingly strange results.
+ This happens because Git directly compares the snapshots of the last commit of the topic branch you're on and the snapshot of the last commit on the `master` branch.
+@@ -263,294 +131,165 @@
+ 
+ If `master` is a direct ancestor of your topic branch, this isn't a problem; but if the two histories have diverged, the diff will look like you're adding all the new stuff in your topic branch and removing everything unique to the `master` branch.
+ 
+-What you really want to see are the changes added to the topic branch -- the work you'll introduce if you merge this branch with `master`.
+-You do that by having Git compare the last commit on your topic branch with the first common ancestor it has with the `master` branch.
++What you really want to see are the changes added to the topic branch – the work you'll introduce if you merge this branch with master.
++You do that by having Git compare the last commit on your topic branch with the first common ancestor it has with the master branch.
+ 
+ Technically, you can do that by explicitly figuring out the common ancestor and then running your diff on it:
+ 
+-[source,console]
+-----
+-$ git merge-base contrib master
+-36c7dba2c95e6bbb78dfa822519ecfec6e1ca649
+-$ git diff 36c7db
+-----
++However, that isn't convenient, so Git provides another shorthand for doing the same thing: the triple-dot syntax.
++In the context of the `diff` command, you can put three periods after another branch to do a `diff` between the last commit of the branch you're on and its common ancestor with another branch:
+ 
+-or, more concisely:
+-
+-[source,console]
+-----
+-$ git diff $(git merge-base contrib master)
+-----
+-
+-However, neither of those is particularly convenient, so Git provides another shorthand for doing the same thing: the triple-dot syntax.
+-In the context of the `git diff` command, you can put three periods after another branch to do a `diff` between the last commit of the branch you're on and its common ancestor with another branch:
+-
+-[source,console]
+-----
+-$ git diff master...contrib
+-----
+-
+-This command shows you only the work your current topic branch has introduced since its common ancestor with `master`.
++This command shows you only the work your current topic branch has introduced since its common ancestor with master.
+ That is a very useful syntax to remember.
+ 
+ ==== Integrating Contributed Work
+ 
+-(((integrating work)))
+ When all the work in your topic branch is ready to be integrated into a more mainline branch, the question is how to do it.
+ Furthermore, what overall workflow do you want to use to maintain your project?
+ You have a number of choices, so we'll cover a few of them.
+ 
+ ===== Merging Workflows
+ 
+-(((workflows, merging)))
+-One basic workflow is to simply merge all that work directly into your `master` branch.
++One simple workflow merges your work into your `master` branch.
+ In this scenario, you have a `master` branch that contains basically stable code.
+-When you have work in a topic branch that you think you've completed, or work that someone else has contributed and you've verified, you merge it into your master branch, delete that just-merged topic branch, and repeat.
+-
+-For instance, if we have a repository with work in two branches named `ruby_client` and `php_client` that looks like <<merwf_a>>, and we merge `ruby_client` followed by `php_client`, your history will end up looking like <<merwf_b>>.
++When you have work in a topic branch that you've done or that someone has contributed and you've verified, you merge it into your master branch, delete the topic branch, and then continue the process.
++If we have a repository with work in two branches named `ruby_client` and `php_client` that looks like <<rmerwf_a>> and merge `ruby_client` first and then `php_client` next, then your history will end up looking like <<rmerwf_b>>.
+ 
+-[[merwf_a]]
+-.History with several topic branches
+-image::images/merging-workflows-1.png[History with several topic branches]
++.History with several topic branches.
++image::images/merging-workflows-1.png[History with several topic branches.]
+ 
+-[[merwf_b]]
+-.After a topic branch merge
+-image::images/merging-workflows-2.png[After a topic branch merge]
++.After a topic branch merge.
++image::images/merging-workflows-2.png[After a topic branch merge.]
+ 
+ That is probably the simplest workflow, but it can possibly be problematic if you're dealing with larger or more stable projects where you want to be really careful about what you introduce.
+ 
+ If you have a more important project, you might want to use a two-phase merge cycle.
+ In this scenario, you have two long-running branches, `master` and `develop`, in which you determine that `master` is updated only when a very stable release is cut and all new code is integrated into the `develop` branch.
+ You regularly push both of these branches to the public repository.
+-Each time you have a new topic branch to merge in (<<merwf_c>>), you merge it into `develop` (<<merwf_d>>); then, when you tag a release, you fast-forward `master` to wherever the now-stable `develop` branch is (<<merwf_e>>).
++Each time you have a new topic branch to merge in (<<rmerwf_c>>), you merge it into `develop` (<<rmerwf_d>>); then, when you tag a release, you fast-forward `master` to wherever the now-stable `develop` branch is (<<rmerwf_e>>).
++
++.Before a topic branch merge.
++image::images/merging-workflows-3.png[Before a topic branch merge.]
++
++.After a topic branch merge.
++image::images/merging-workflows-4.png[After a topic branch merge.]
++
++.After a project release.
++image::images/merging-workflows-5.png[After a topic branch release.]
+ 
+-[[merwf_c]]
+-.Before a topic branch merge
+-image::images/merging-workflows-3.png[Before a topic branch merge]
+-
+-[[merwf_d]]
+-.After a topic branch merge
+-image::images/merging-workflows-4.png[After a topic branch merge]
+-
+-[[merwf_e]]
+-.After a project release
+-image::images/merging-workflows-5.png[After a topic branch release]
+-
+-This way, when people clone your project's repository, they can either check out `master` to build the latest stable version and keep up to date on that easily, or they can check out `develop`, which is the more cutting-edge content.
+-You can also extend this concept by having an `integrate` branch where all the work is merged together.
+-Then, when the codebase on that branch is stable and passes tests, you merge it into a `develop` branch; and when that has proven itself stable for a while, you fast-forward your `master` branch.
++This way, when people clone your project's repository, they can either check out master to build the latest stable version and keep up to date on that easily, or they can check out develop, which is the more cutting-edge stuff.
++You can also continue this concept, having an integrate branch where all the work is merged together.
++Then, when the codebase on that branch is stable and passes tests, you merge it into a develop branch; and when that has proven itself stable for a while, you fast-forward your master branch.
+ 
+ ===== Large-Merging Workflows
+ 
+-(((workflows, "merging (large)")))
+-The Git project has four long-running branches: `master`, `next`, and `seen` (formerly 'pu' -- proposed updates) for new work, and `maint` for maintenance backports.
+-When new work is introduced by contributors, it's collected into topic branches in the maintainer's repository in a manner similar to what we've described (see <<merwf_f>>).
++The Git project has four long-running branches: `master`, `next`, and `pu` (proposed updates) for new work, and `maint` for maintenance backports.
++When new work is introduced by contributors, it's collected into topic branches in the maintainer's repository in a manner similar to what we've described (see <<rmerwf_f>>).
+ At this point, the topics are evaluated to determine whether they're safe and ready for consumption or whether they need more work.
+ If they're safe, they're merged into `next`, and that branch is pushed up so everyone can try the topics integrated together.
+ 
+-[[merwf_f]]
+-.Managing a complex series of parallel contributed topic branches
+-image::images/large-merges-1.png[Managing a complex series of parallel contributed topic branches]
+-
+-If the topics still need work, they're merged into `seen` instead.
+-When it's determined that they're totally stable, the topics are re-merged into `master`.
+-The `next` and `seen` branches are then rebuilt from the `master`.
+-This means `master` almost always moves forward, `next` is rebased occasionally, and `seen` is rebased even more often:
++.Managing a complex series of parallel contributed topic branches.
++image::images/large-merges-1.png[Managing a complex series of parallel contributed topic branches.]
+ 
+-.Merging contributed topic branches into long-term integration branches
+-image::images/large-merges-2.png[Merging contributed topic branches into long-term integration branches]
++If the topics still need work, they're merged into `pu` instead.
++When it's determined that they're totally stable, the topics are re-merged into `master` and are then rebuilt from the topics that were in `next` but didn't yet graduate to `master`.
++This means `master` almost always moves forward, `next` is rebased occasionally, and `pu` is rebased even more often:
++
++.Merging contributed topic branches into long-term integration branches.
++image::images/large-merges-2.png[Merging contributed topic branches into long-term integration branches.]
+ 
+ When a topic branch has finally been merged into `master`, it's removed from the repository.
+ The Git project also has a `maint` branch that is forked off from the last release to provide backported patches in case a maintenance release is required.
+ Thus, when you clone the Git repository, you have four branches that you can check out to evaluate the project in different stages of development, depending on how cutting edge you want to be or how you want to contribute; and the maintainer has a structured workflow to help them vet new contributions.
+-The Git project's workflow is specialized.
+-To clearly understand this you could check out the https://github.com/git/git/blob/master/Documentation/howto/maintain-git.txt[Git Maintainer's guide].
+ 
+-[[_rebase_cherry_pick]]
+-===== Rebasing and Cherry-Picking Workflows
++===== Rebasing and Cherry Picking Workflows
+ 
+-(((workflows, rebasing and cherry-picking)))
+-Other maintainers prefer to rebase or cherry-pick contributed work on top of their `master` branch, rather than merging it in, to keep a mostly linear history.
+-When you have work in a topic branch and have determined that you want to integrate it, you move to that branch and run the rebase command to rebuild the changes on top of your current `master` (or `develop`, and so on) branch.
++Other maintainers prefer to rebase or cherry-pick contributed work on top of their master branch, rather than merging it in, to keep a mostly linear history.
++When you have work in a topic branch and have determined that you want to integrate it, you move to that branch and run the rebase command to rebuild the changes on top of your current master (or `develop`, and so on) branch.
+ If that works well, you can fast-forward your `master` branch, and you'll end up with a linear project history.
+ 
+-(((git commands, cherry-pick)))
+ The other way to move introduced work from one branch to another is to cherry-pick it.
+ A cherry-pick in Git is like a rebase for a single commit.
+ It takes the patch that was introduced in a commit and tries to reapply it on the branch you're currently on.
+ This is useful if you have a number of commits on a topic branch and you want to integrate only one of them, or if you only have one commit on a topic branch and you'd prefer to cherry-pick it rather than run rebase.
+ For example, suppose you have a project that looks like this:
+ 
+-.Example history before a cherry-pick
+-image::images/rebasing-1.png[Example history before a cherry-pick]
+-
+-If you want to pull commit `e43a6` into your `master` branch, you can run:
++.Example history before a cherry-pick.
++image::images/rebasing-1.png[Example history before a cherry-pick.]
+ 
+-[source,console]
+-----
+-$ git cherry-pick e43a6
+-Finished one cherry-pick.
+-[master]: created a0a41a9: "More friendly message when locking the index fails."
+- 3 files changed, 17 insertions(+), 3 deletions(-)
+-----
++If you want to pull commit `e43a6` into your master branch, you can run
+ 
+ This pulls the same change introduced in `e43a6`, but you get a new commit SHA-1 value, because the date applied is different.
+ Now your history looks like this:
+ 
+-.History after cherry-picking a commit on a topic branch
+-image::images/rebasing-2.png[History after cherry-picking a commit on a topic branch]
++.History after cherry-picking a commit on a topic branch.
++image::images/rebasing-2.png[History after cherry-picking a commit on a topic branch.]
+ 
+ Now you can remove your topic branch and drop the commits you didn't want to pull in.
+ 
+-===== Rerere
+-
+-(((git commands, rerere)))(((rerere)))
+ If you're doing lots of merging and rebasing, or you're maintaining a long-lived topic branch, Git has a feature called ``rerere'' that can help.
+ 
+-Rerere stands for ``reuse recorded resolution'' -- it's a way of shortcutting manual conflict resolution.
++Rerere stands for ``reuse recorded resolution'' – it's a way of shortcutting manual conflict resolution.
+ When rerere is enabled, Git will keep a set of pre- and post-images from successful merges, and if it notices that there's a conflict that looks exactly like one you've already fixed, it'll just use the fix from last time, without bothering you with it.
+ 
+ This feature comes in two parts: a configuration setting and a command.
+ The configuration setting is `rerere.enabled`, and it's handy enough to put in your global config:
+ 
+-[source,console]
+-----
+-$ git config --global rerere.enabled true
+-----
+-
+ Now, whenever you do a merge that resolves conflicts, the resolution will be recorded in the cache in case you need it in the future.
+ 
+ If you need to, you can interact with the rerere cache using the `git rerere` command.
+ When it's invoked alone, Git checks its database of resolutions and tries to find a match with any current merge conflicts and resolve them (although this is done automatically if `rerere.enabled` is set to `true`).
+ There are also subcommands to see what will be recorded, to erase specific resolution from the cache, and to clear the entire cache.
+-We will cover rerere in more detail in <<ch07-git-tools#ref_rerere>>.
++We will cover rerere in more detail in <<ch07-git-tools#r_rerere>>.
+ 
+-[[_tagging_releases]]
+ ==== Tagging Your Releases
+ 
+-(((tags)))(((tags, signing)))
+-When you've decided to cut a release, you'll probably want to assign a tag so you can re-create that release at any point going forward.
+-You can create a new tag as discussed in <<ch02-git-basics-chapter#ch02-git-basics-chapter>>.
++When you've decided to cut a release, you'll probably want to drop a tag so you can re-create that release at any point going forward.
++You can create a new tag as discussed in <<ch02-git-basics#ch02-git-basics>>.
+ If you decide to sign the tag as the maintainer, the tagging may look something like this:
+ 
+-[source,console]
+-----
+-$ git tag -s v1.5 -m 'my signed 1.5 tag'
+-You need a passphrase to unlock the secret key for
+-user: "Scott Chacon <[e-mail]>"
+-1024-bit DSA key, ID F721C45A, created 2009-02-09
+-----
+-
+ If you do sign your tags, you may have the problem of distributing the public PGP key used to sign your tags.
+ The maintainer of the Git project has solved this issue by including their public key as a blob in the repository and then adding a tag that points directly to that content.
+ To do this, you can figure out which key you want by running `gpg --list-keys`:
+ 
+-[source,console]
+-----
+-$ gpg --list-keys
+-/Users/schacon/.gnupg/pubring.gpg
+----------------------------------
+-pub   1024D/F721C45A 2009-02-09 [expires: 2010-02-09]
+-uid                  Scott Chacon <[e-mail]>
+-sub   2048g/45D02282 2009-02-09 [expires: 2010-02-09]
+-----
+-
+ Then, you can directly import the key into the Git database by exporting it and piping that through `git hash-object`, which writes a new blob with those contents into Git and gives you back the SHA-1 of the blob:
+ 
+-[source,console]
+-----
+-$ gpg -a --export F721C45A | git hash-object -w --stdin
+-659ef797d181633c87ec71ac3f9ba29fe5775b92
+-----
+-
+ Now that you have the contents of your key in Git, you can create a tag that points directly to it by specifying the new SHA-1 value that the `hash-object` command gave you:
+ 
+-[source,console]
+-----
+-$ git tag -a maintainer-pgp-pub 659ef797d181633c87ec71ac3f9ba29fe5775b92
+-----
+-
+ If you run `git push --tags`, the `maintainer-pgp-pub` tag will be shared with everyone.
+ If anyone wants to verify a tag, they can directly import your PGP key by pulling the blob directly out of the database and importing it into GPG:
+ 
+-[source,console]
+-----
+-$ git show maintainer-pgp-pub | gpg --import
+-----
+-
+ They can use that key to verify all your signed tags.
+ Also, if you include instructions in the tag message, running `git show <tag>` will let you give the end user more specific instructions about tag verification.
+ 
+-[[_build_number]]
+ ==== Generating a Build Number
+ 
+-(((build numbers)))(((git commands, describe)))
+ Because Git doesn't have monotonically increasing numbers like 'v123' or the equivalent to go with each commit, if you want to have a human-readable name to go with a commit, you can run `git describe` on that commit.
+-In response, Git generates a string consisting of the name of the most recent tag earlier than that commit, followed by the number of commits since that tag, followed finally by a partial SHA-1 value of the commit being described (prefixed with the letter "g" meaning Git):
+-
+-[source,console]
+-----
+-$ git describe master
+-v1.6.2-rc1-20-g8c5b85c
+-----
++Git gives you the name of the nearest tag with the number of commits on top of that tag and a partial SHA-1 value of the commit you're describing:
+ 
+ This way, you can export a snapshot or build and name it something understandable to people.
+ In fact, if you build Git from source code cloned from the Git repository, `git --version` gives you something that looks like this.
+-If you're describing a commit that you have directly tagged, it gives you simply the tag name.
++If you're describing a commit that you have directly tagged, it gives you the tag name.
+ 
+-By default, the `git describe` command requires annotated tags (tags created with the `-a` or `-s` flag); if you want to take advantage of lightweight (non-annotated) tags as well, add the `--tags` option to the command.
+-You can also use this string as the target of a `git checkout` or `git show` command, although it relies on the abbreviated SHA-1 value at the end, so it may not be valid forever.
++The `git describe` command favors annotated tags (tags created with the `-a` or `-s` flag), so release tags should be created this way if you're using `git describe`, to ensure the commit is named properly when described.
++You can also use this string as the target of a checkout or show command, although it relies on the abbreviated SHA-1 value at the end, so it may not be valid forever.
+ For instance, the Linux kernel recently jumped from 8 to 10 characters to ensure SHA-1 object uniqueness, so older `git describe` output names were invalidated.
+ 
+-[[_preparing_release]]
+ ==== Preparing a Release
+ 
+-(((releasing)))(((git commands, archive)))
+ Now you want to release a build.
+ One of the things you'll want to do is create an archive of the latest snapshot of your code for those poor souls who don't use Git.
+ The command to do this is `git archive`:
+ 
+-[source,console]
+-----
+-$ git archive master --prefix='project/' | gzip > `git describe master`.tar.gz
+-$ ls *.tar.gz
+-v1.6.2-rc1-20-g8c5b85c.tar.gz
+-----
+-
+-If someone opens that tarball, they get the latest snapshot of your project under a `project` directory.
++If someone opens that tarball, they get the latest snapshot of your project under a project directory.
+ You can also create a zip archive in much the same way, but by passing the `--format=zip` option to `git archive`:
+ 
+-[source,console]
+-----
+-$ git archive master --prefix='project/' --format=zip > `git describe master`.zip
+-----
+-
+ You now have a nice tarball and a zip archive of your project release that you can upload to your website or email to people.
+ 
+-[[_the_shortlog]]
+ ==== The Shortlog
+ 
+-(((git commands, shortlog)))
+ It's time to email your mailing list of people who want to know what's happening in your project.
+ A nice way of quickly getting a sort of changelog of what has been added to your project since your last release or email is to use the `git shortlog` command.
+ It summarizes all the commits in the range you give it; for example, the following gives you a summary of all the commits since your last release, if your last release was named v1.0.1:
+ 
+-[source,console]
+-----
+-$ git shortlog --no-merges master --not v1.0.1
+-Chris Wanstrath (6):
+-      Add support for annotated tags to Grit::Tag
+-      Add packed-refs annotated tag support.
+-      Add Grit::Commit#to_patch
+-      Update version and History.txt
+-      Remove stray `puts`
+-      Make ls_tree ignore nils
+-
+-Tom Preston-Werner (4):
+-      fix dates in history
+-      dynamic version method
+-      Version bump to 1.0.2
+-      Regenerated gemspec for version 1.0.2
+-----
+-
+ You get a clean summary of all the commits since v1.0.1, grouped by author, that you can email to your list.
+diff -au ../../git/progit2/progit2/book/06-github/sections/1-setting-up-account.asc /tmp/book/06-github/sections/1-setting-up-account.asc.tmp
+--- ../../git/progit2/progit2/book/06-github/sections/1-setting-up-account.asc	2020-07-04 16:36:46.730685537 +0900
++++ /tmp/book/06-github/sections/1-setting-up-account.asc.tmp	2020-10-25 09:24:25.762971711 +0900
+@@ -1,22 +1,18 @@
+ === Account Setup and Configuration
+ 
+-(((GitHub, user accounts)))
+ The first thing you need to do is set up a free user account.
+ Simply visit https://github.com[], choose a user name that isn't already taken, provide an email address and a password, and click the big green ``Sign up for GitHub'' button.
+ 
+-.The GitHub sign-up form
+-image::images/signup.png[The GitHub sign-up form]
++.The GitHub sign-up form.
++image::images/signup.png[The GitHub sign-up form.]
+ 
+ The next thing you'll see is the pricing page for upgraded plans, but it's safe to ignore this for now.
+ GitHub will send you an email to verify the address you provided.
+-Go ahead and do this; it's pretty important (as we'll see later).
++Go ahead and do this, it's pretty important (as we'll see later).
+ 
+-[NOTE]
+ ====
+-GitHub provides almost all of its functionality with free accounts, except some advanced features.
+-
+-GitHub's paid plans include advanced tools and features as well as increased limits for free services, but we won't be covering those in this book.
+-To get more information about available plans and their comparison, visit https://github.com/pricing[].
++GitHub provides all of its functionality with free accounts, with the limitation that all of your projects are fully public (everyone has read access).
++GitHub's paid plans include a set number of private projects, but we won't be covering those in this book.
+ ====
+ 
+ Clicking the Octocat logo at the top-left of the screen will take you to your dashboard page.
+@@ -24,43 +20,40 @@
+ 
+ ==== SSH Access
+ 
+-(((SSH keys, with GitHub)))
+ As of right now, you're fully able to connect with Git repositories using the `https://` protocol, authenticating with the username and password you just set up.
+ However, to simply clone public projects, you don't even need to sign up - the account we just created comes into play when we fork projects and push to our forks a bit later.
+ 
+ If you'd like to use SSH remotes, you'll need to configure a public key.
+-If you don't already have one, see <<ch04-git-on-the-server#_generate_ssh_key>>.
++(If you don't already have one, see <<ch04-git-server#r_generate_ssh_key>>.)
+ Open up your account settings using the link at the top-right of the window:
+ 
+-.The ``Account settings'' link
+-image::images/account-settings.png[The ``Account settings'' link]
++.The ``Account settings'' link.
++image::images/account-settings.png[The ``Account settings'' link.]
+ 
+ Then select the ``SSH keys'' section along the left-hand side.
+ 
+-.The ``SSH keys'' link
+-image::images/ssh-keys.png[The ``SSH keys'' link]
++.The ``SSH keys'' link.
++image::images/ssh-keys.png[The ``SSH keys'' link.]
+ 
+ From there, click the "`Add an SSH key`" button, give your key a name, paste the contents of your `~/.ssh/id_rsa.pub` (or whatever you named it) public-key file into the text area, and click ``Add key''.
+ 
+-[NOTE]
+ ====
+ Be sure to name your SSH key something you can remember.
+ You can name each of your keys (e.g. "My Laptop" or "Work Account") so that if you need to revoke a key later, you can easily tell which one you're looking for.
+ ====
+ 
+-[[_personal_avatar]]
+ ==== Your Avatar
+ 
+ Next, if you wish, you can replace the avatar that is generated for you with an image of your choosing.
+ First go to the ``Profile'' tab (above the SSH Keys tab) and click ``Upload new picture''.
+ 
+-.The ``Profile'' link
+-image::images/your-profile.png[The ``Profile'' link]
++.The ``Profile'' link.
++image::images/your-profile.png[The ``Profile'' link.]
+ 
+ We'll choose a copy of the Git logo that is on our hard drive and then we get a chance to crop it.
+ 
+ .Crop your avatar
+-image::images/avatar-crop.png[Crop your uploaded avatar]
++image::images/avatar-crop.png[Crop your uploaded avatar.]
+ 
+ Now anywhere you interact on the site, people will see your avatar next to your username.
+ 
+@@ -71,11 +64,10 @@
+ The way that GitHub maps your Git commits to your user is by email address.
+ If you use multiple email addresses in your commits and you want GitHub to link them up properly, you need to add all the email addresses you have used to the Emails section of the admin section.
+ 
+-[[_add_email_addresses]]
+ .Add email addresses
+-image::images/email-settings.png[Add all your email addresses]
++image::images/email-settings.png[Add all your email addresses.]
+ 
+-In <<_add_email_addresses>> we can see some of the different states that are possible.
++In <<r_add_email_addresses>> we can see some of the different states that are possible.
+ The top address is verified and set as the primary address, meaning that is where you'll get any notifications and receipts.
+ The second address is verified and so can be set as the primary if you wish to switch them.
+ The final address is unverified, meaning that you can't make it your primary address.
+diff -au ../../git/progit2/progit2/book/06-github/sections/2-contributing.asc /tmp/book/06-github/sections/2-contributing.asc.tmp
+--- ../../git/progit2/progit2/book/06-github/sections/2-contributing.asc	2020-09-30 09:43:39.046514305 +0900
++++ /tmp/book/06-github/sections/2-contributing.asc.tmp	2020-10-25 09:24:25.769972041 +0900
+@@ -4,131 +4,72 @@
+ 
+ ==== Forking Projects
+ 
+-(((forking)))
+-If you want to contribute to an existing project to which you don't have push access, you can ``fork'' the project.
+-When you ``fork'' a project, GitHub will make a copy of the project that is entirely yours; it lives in your namespace, and you can push to it.
++If you want to contribute to an existing project to which you don’t have push access, you can ``fork'' the project.
++What this means is that GitHub will make a copy of the project that is entirely yours; it lives in your user's namespace, and you can push to it.
+ 
+-[NOTE]
+ ====
+ Historically, the term ``fork'' has been somewhat negative in context, meaning that someone took an open source project in a different direction, sometimes creating a competing project and splitting the contributors.
+ In GitHub, a ``fork'' is simply the same project in your own namespace, allowing you to make changes to a project publicly as a way to contribute in a more open manner.
+ ====
+ 
+-This way, projects don't have to worry about adding users as collaborators to give them push access.
++This way, projects don’t have to worry about adding users as collaborators to give them push access.
+ People can fork a project, push to it, and contribute their changes back to the original repository by creating what's called a Pull Request, which we'll cover next.
+ This opens up a discussion thread with code review, and the owner and the contributor can then communicate about the change until the owner is happy with it, at which point the owner can merge it in.
+ 
+ To fork a project, visit the project page and click the ``Fork'' button at the top-right of the page.
+ 
+-.The ``Fork'' button
+-image::images/forkbutton.png[The ``Fork'' button]
++.The ``Fork'' button.
++image::images/forkbutton.png[The ``Fork'' button.]
+ 
+ After a few seconds, you'll be taken to your new project page, with your own writeable copy of the code.
+ 
+-
+-[[ch06-github_flow]]
+ ==== The GitHub Flow
+ 
+-(((GitHub, Flow)))
+ GitHub is designed around a particular collaboration workflow, centered on Pull Requests.
+ This flow works whether you're collaborating with a tightly-knit team in a single shared repository, or a globally-distributed company or network of strangers contributing to a project through dozens of forks.
+-It is centered on the <<ch03-git-branching#_topic_branch>> workflow covered in <<ch03-git-branching#ch03-git-branching>>.
++It is centered on the <<ch03-git-branching#r_topic_branch>> workflow covered in <<ch03-git-branching#ch03-git-branching>>.
+ 
+ Here's how it generally works:
+ 
+-1. Fork the project.
+-2. Create a topic branch from `master`.
+-3. Make some commits to improve the project.
+-4. Push this branch to your GitHub project.
+-5. Open a Pull Request on GitHub.
+-6. Discuss, and optionally continue committing.
+-7. The project owner merges or closes the Pull Request.
+-8. Sync the updated master back to your fork.
++1. Create a topic branch from `master`.
++2. Make some commits to improve the project.
++3. Push this branch to your GitHub project.
++4. Open a Pull Request on GitHub.
++5. Discuss, and optionally continue committing.
++6. The project owner merges or closes the Pull Request.
+ 
+-This is basically the Integration Manager workflow covered in <<ch05-distributed-git#_integration_manager>>, but instead of using email to communicate and review changes, teams use GitHub's web based tools.
++This is basically the Integration Manager workflow covered in <<ch05-distributed-git#r_integration_manager>>, but instead of using email to communicate and review changes, teams use GitHub's web based tools.
+ 
+ Let's walk through an example of proposing a change to an open source project hosted on GitHub using this flow.
+ 
+-[TIP]
+-====
+-You can use the official *GitHub CLI* tool instead of the GitHub web interface for most things.
+-The tool can be used on Windows, MacOS, and Linux systems.
+-Go to the https://cli.github.com/[GitHub CLI homepage] for installation instructions and the manual.
+-====
+-
+ ===== Creating a Pull Request
+ 
+ Tony is looking for code to run on his Arduino programmable microcontroller and has found a great program file on GitHub at https://github.com/schacon/blink[].
+ 
+-.The project we want to contribute to
+-image::images/blink-01-start.png[The project we want to contribute to]
++.The project we want to contribute to.
++image::images/blink-01-start.png[The project we want to contribute to.]
+ 
+-The only problem is that the blinking rate is too fast.
+-We think it's much nicer to wait 3 seconds instead of 1 in between each state change.
++The only problem is that the blinking rate is too fast, we think it's much nicer to wait 3 seconds instead of 1 in between each state change.
+ So let's improve the program and submit it back to the project as a proposed change.
+ 
+ First, we click the 'Fork' button as mentioned earlier to get our own copy of the project.
+ Our user name here is ``tonychacon'' so our copy of this project is at `https://github.com/tonychacon/blink` and that's where we can edit it.
+ We will clone it locally, create a topic branch, make the code change and finally push that change back up to GitHub.
+ 
+-[source,console]
+-----
+-$ git clone https://github.com/tonychacon/blink <1>
+-Cloning into 'blink'...
+-
+-$ cd blink
+-$ git checkout -b slow-blink <2>
+-Switched to a new branch 'slow-blink'
+-
+-$ sed -i '' 's/1000/3000/' blink.ino (macOS) <3>
+-# If you're on a Linux system, do this instead:
+-# $ sed -i 's/1000/3000/' blink.ino <3>
+-
+-$ git diff --word-diff <4>
+-diff --git a/blink.ino b/blink.ino
+-index 15b9911..a6cc5a5 100644
+---- a/blink.ino
+-+++ b/blink.ino
+-@@ -18,7 +18,7 @@ void setup() {
+-// the loop routine runs over and over again forever:
+-void loop() {
+-  digitalWrite(led, HIGH);   // turn the LED on (HIGH is the voltage level)
+-  [-delay(1000);-]{+delay(3000);+}               // wait for a second
+-  digitalWrite(led, LOW);    // turn the LED off by making the voltage LOW
+-  [-delay(1000);-]{+delay(3000);+}               // wait for a second
+-}
+-
+-$ git commit -a -m 'Change delay to 3 seconds' <5>
+-[slow-blink 5ca509d] Change delay to 3 seconds
+- 1 file changed, 2 insertions(+), 2 deletions(-)
+-
+-$ git push origin slow-blink <6>
+-Username for 'https://github.com': tonychacon
+-Password for 'https://[e-mail]':
+-Counting objects: 5, done.
+-Delta compression using up to 8 threads.
+-Compressing objects: 100% (3/3), done.
+-Writing objects: 100% (3/3), 340 bytes | 0 bytes/s, done.
+-Total 3 (delta 1), reused 0 (delta 0)
+-To https://github.com/tonychacon/blink
+- * [new branch]      slow-blink -> slow-blink
+-----
+-
+-<1> Clone our fork of the project locally.
+-<2> Create a descriptive topic branch.
+-<3> Make our change to the code.
+-<4> Check that the change is good.
+-<5> Commit our change to the topic branch.
+-<6> Push our new topic branch back up to our GitHub fork.
++<1> Clone our fork of the project locally
++<2> Create a descriptive topic branch
++<3> Make our change to the code
++<4> Check that the change is good
++<5> Commit our change to the topic branch
++<6> Push our new topic branch back up to our GitHub fork
+ 
+-Now if we go back to our fork on GitHub, we can see that GitHub noticed that we pushed a new topic branch up and presents us with a big green button to check out our changes and open a Pull Request to the original project.
++Now if we go back to our fork on GitHub, we can see that GitHub noticed that we pushed a new topic branch up and present us with a big green button to check out our changes and open a Pull Request to the original project.
+ 
+ You can alternatively go to the ``Branches'' page at `https://github.com/<user>/<project>/branches` to locate your branch and open a new Pull Request from there.
+ 
+ .Pull Request button
+ image::images/blink-02-pr.png[Pull Request button]
+ 
+-(((GitHub, pull requests)))
+ If we click that green button, we'll see a screen that asks us to give our Pull Request a title and description.
+ It is almost always worthwhile to put some effort into this, since a good description helps the owner of the original project determine what you were trying to do, whether your proposed changes are correct, and whether accepting the changes would improve the original project.
+ 
+@@ -139,69 +80,50 @@
+ 
+ When you hit the 'Create pull request' button on this screen, the owner of the project you forked will get a notification that someone is suggesting a change and will link to a page that has all of this information on it.
+ 
+-[NOTE]
+ ====
+-Though Pull Requests are used commonly for public projects like this when the contributor has a complete change ready to be made, it's also often used in internal projects _at the beginning_ of the development cycle.
+-Since you can keep pushing to the topic branch even *after* the Pull Request is opened, it's often opened early and used as a way to iterate on work as a team within a context, rather than opened at the very end of the process.
++Though Pull Requests are used commonly for public projects like this when the contributor has a complete change ready to be made, it's also often used in internal projects _at the beginning_ of the development cycle. Since you can keep pushing to the topic branch even *after* the Pull Request is opened, it's often opened early and used as a way to iterate on work as a team within a context, rather than opened at the very end of the process.
+ ====
+ 
+ ===== Iterating on a Pull Request
+ 
+-At this point, the project owner can look at the suggested change and merge it, reject it or comment on it.
+-Let's say that he likes the idea, but would prefer a slightly longer time for the light to be off than on.
++At this point, the project owner can look at the suggested change and merge it, reject it or comment on it. Let's say that he likes the idea, but would prefer a slightly longer time for the light to be off than on.
+ 
+-Where this conversation may take place over email in the workflows presented in <<ch05-distributed-git#ch05-distributed-git>>, on GitHub this happens online.
+-The project owner can review the unified diff and leave a comment by clicking on any of the lines.
++Where this conversation may take place over email in the workflows presented in <<ch05-distributed-git#ch05-distributed-git>>, on GitHub this happens online. The project owner can review the unified diff and leave a comment by clicking on any of the lines.
+ 
+ .Comment on a specific line of code in a Pull Request
+ image::images/blink-04-pr-comment.png[PR line comment]
+ 
+-Once the maintainer makes this comment, the person who opened the Pull Request (and indeed, anyone else watching the repository) will get a notification.
+-We'll go over customizing this later, but if he had email notifications turned on, Tony would get an email like this:
++Once the maintainer makes this comment, the person who opened the Pull Request (and indeed, anyone else watching the repository) will get a notification. We'll go over customizing this later, but if he had email notifications turned on, Tony would get an email like this:
+ 
+-[[_email_notification]]
+ .Comments sent as email notifications
+ image::images/blink-04-email.png[Email notification]
+ 
+-Anyone can also leave general comments on the Pull Request.
+-In <<_pr_discussion>> we can see an example of the project owner both commenting on a line of code and then leaving a general comment in the discussion section.
+-You can see that the code comments are brought into the conversation as well.
++Anyone can also leave general comments on the Pull Request. In <<r_pr_discussion>> we can see an example of the project owner both commenting on a line of code and then leaving a general comment in the discussion section. You can see that the code comments are brought into the conversation as well.
+ 
+-[[_pr_discussion]]
+ .Pull Request discussion page
+ image::images/blink-05-general-comment.png[PR discussion page]
+ 
+ Now the contributor can see what they need to do in order to get their change accepted.
+-Luckily this is very straightforward.
++Luckily this is also a very simple thing to do.
+ Where over email you may have to re-roll your series and resubmit it to the mailing list, with GitHub you simply commit to the topic branch again and push, which will automatically update the Pull Request.
+-In <<_pr_final>> you can also see that the old code comment has been collapsed in the updated Pull Request, since it was made on a line that has since been changed.
++In <<r_pr_final>> you can also see that the old code comment has been collapsed in the updated Pull Request, since it was made on a line that has since been changed.
+ 
+ Adding commits to an existing Pull Request doesn't trigger a notification, so once Tony has pushed his corrections he decides to leave a comment to inform the project owner that he made the requested change.
+ 
+-[[_pr_final]]
+ .Pull Request final
+ image::images/blink-06-final.png[PR final]
+ 
+-An interesting thing to notice is that if you click on the ``Files Changed'' tab on this Pull Request, you'll get the ``unified'' diff -- that is, the total aggregate difference that would be introduced to your main branch if this topic branch was merged in.
+-In `git diff` terms, it basically automatically shows you `git diff master...<branch>` for the branch this Pull Request is based on.
+-See <<ch05-distributed-git#_what_is_introduced>> for more about this type of diff.
++An interesting thing to notice is that if you click on the ``Files Changed'' tab on this Pull Request, you'll get the ``unified'' diff -- that is, the total aggregate difference that would be introduced to your main branch if this topic branch was merged in. In `git diff` terms, it basically automatically shows you `git diff master...<branch>` for the branch this Pull Request is based on. See <<ch05-distributed-git#r_what_is_introduced>> for more about this type of diff.
+ 
+-The other thing you'll notice is that GitHub checks to see if the Pull Request merges cleanly and provides a button to do the merge for you on the server.
+-This button only shows up if you have write access to the repository and a trivial merge is possible.
+-If you click it GitHub will perform a ``non-fast-forward'' merge, meaning that even if the merge *could* be a fast-forward, it will still create a merge commit.
++The other thing you'll notice is that GitHub checks to see if the Pull Request merges cleanly and provides a button to do the merge for you on the server. This button only shows up if you have write access to the repository and a trivial merge is possible. If you click it GitHub will perform a ``non-fast-forward'' merge, meaning that even if the merge *could* be a fast-forward, it will still create a merge commit.
+ 
+-If you would prefer, you can simply pull the branch down and merge it locally.
+-If you merge this branch into the `master` branch and push it to GitHub, the Pull Request will automatically be closed.
++If you would prefer, you can simply pull the branch down and merge it locally. If you merge this branch into the `master` branch and push it to GitHub, the Pull Request will automatically be closed.
+ 
+-This is the basic workflow that most GitHub projects use.
+-Topic branches are created, Pull Requests are opened on them, a discussion ensues, possibly more work is done on the branch and eventually the request is either closed or merged.
++This is the basic workflow that most GitHub projects use. Topic branches are created, Pull Requests are opened on them, a discussion ensues, possibly more work is done on the branch and eventually the request is either closed or merged.
+ 
+-[NOTE]
+ .Not Only Forks
+ ====
+-It's important to note that you can also open a Pull Request between two branches in the same repository.
+-If you're working on a feature with someone and you both have write access to the project, you can push a topic branch to the repository and open a Pull Request on it to the `master` branch of that same project to initiate the code review and discussion process.
+-No forking necessary.
++It's important to note that you can also open a Pull Request between two branches in the same repository. If you're working on a feature with someone and you both have write access to the project, you can push a topic branch to the repository and open a Pull Request on it to the `master` branch of that same project to initiate the code review and discussion process. No forking necessary.
+ ====
+ 
+ ==== Advanced Pull Requests
+@@ -210,339 +132,151 @@
+ 
+ ===== Pull Requests as Patches
+ 
+-It's important to understand that many projects don't really think of Pull Requests as queues of perfect patches that should apply cleanly in order, as most mailing list-based projects think of patch series contributions.
+-Most GitHub projects think about Pull Request branches as iterative conversations around a proposed change, culminating in a unified diff that is applied by merging.
++It's important to understand that many projects don't really think of Pull Requests as queues of perfect patches that should apply cleanly in order, as most mailing list-based projects think of patch series contributions. Most GitHub projects think about Pull Request branches as iterative conversations around a proposed change, culminating in a unified diff that is applied by merging.
++
++This is an important distinction, because generally the change is suggested before the code is thought to be perfect, which is far more rare with mailing list based patch series contributions. This enables an earlier conversation with the maintainers so that arriving at the proper solution is more of a community effort. When code is proposed with a Pull Request and the maintainers or community suggest a change, the patch series is generally not re-rolled, but instead the difference is pushed as a new commit to the branch, moving the conversation forward with the context of the previous work intact.
+ 
+-This is an important distinction, because generally the change is suggested before the code is thought to be perfect, which is far more rare with mailing list based patch series contributions.
+-This enables an earlier conversation with the maintainers so that arriving at the proper solution is more of a community effort.
+-When code is proposed with a Pull Request and the maintainers or community suggest a change, the patch series is generally not re-rolled, but instead the difference is pushed as a new commit to the branch, moving the conversation forward with the context of the previous work intact.
+-
+-For instance, if you go back and look again at <<_pr_final>>, you'll notice that the contributor did not rebase his commit and send another Pull Request.
+-Instead they added new commits and pushed them to the existing branch.
+-This way if you go back and look at this Pull Request in the future, you can easily find all of the context of why decisions were made.
+-Pushing the ``Merge'' button on the site purposefully creates a merge commit that references the Pull Request so that it's easy to go back and research the original conversation if necessary.
++For instance, if you go back and look again at <<r_pr_final>>, you'll notice that the contributor did not rebase his commit and send another Pull Request. Instead they added new commits and pushed them to the existing branch. This way if you go back and look at this Pull Request in the future, you can easily find all of the context of why decisions were made. Pushing the ``Merge'' button on the site purposefully creates a merge commit that references the Pull Request so that it's easy to go back and research the original conversation if necessary.
+ 
+ ===== Keeping up with Upstream
+ 
+-If your Pull Request becomes out of date or otherwise doesn't merge cleanly, you will want to fix it so the maintainer can easily merge it.
+-GitHub will test this for you and let you know at the bottom of every Pull Request if the merge is trivial or not.
++If your Pull Request becomes out of date or otherwise doesn't merge cleanly, you will want to fix it so the maintainer can easily merge it. GitHub will test this for you and let you know at the bottom of every Pull Request if the merge is trivial or not.
+ 
+-[[_pr_fail]]
+ .Pull Request does not merge cleanly
+ image::images/pr-01-fail.png[PR merge failure]
+ 
+-If you see something like <<_pr_fail>>, you'll want to fix your branch so that it turns green and the maintainer doesn't have to do extra work.
++If you see something like <<r_pr_fail>>, you'll want to fix your branch so that it turns green and the maintainer doesn't have to do extra work.
+ 
+-You have two main options in order to do this.
+-You can either rebase your branch on top of whatever the target branch is (normally the `master` branch of the repository you forked), or you can merge the target branch into your branch.
++You have two main options in order to do this. You can either rebase your branch on top of whatever the target branch is (normally the `master` branch of the repository you forked), or you can merge the target branch into your branch.
+ 
+-Most developers on GitHub will choose to do the latter, for the same reasons we just went over in the previous section.
+-What matters is the history and the final merge, so rebasing isn't getting you much other than a slightly cleaner history and in return is *far* more difficult and error prone.
++Most developers on GitHub will choose to do the latter, for the same reasons we just went over in the previous section. What matters is the history and the final merge, so rebasing isn't getting you much other than a slightly cleaner history and in return is *far* more difficult and error prone.
+ 
+ If you want to merge in the target branch to make your Pull Request mergeable, you would add the original repository as a new remote, fetch from it, merge the main branch of that repository into your topic branch, fix any issues and finally push it back up to the same branch you opened the Pull Request on.
+ 
+-For example, let's say that in the ``tonychacon'' example we were using before, the original author made a change that would create a conflict in the Pull Request.
+-Let's go through those steps.
++For example, let's say that in the ``tonychacon'' example we were using before, the original author made a change that would create a conflict in the Pull Request. Let's go through those steps.
+ 
+-[source,console]
+-----
+-$ git remote add upstream https://github.com/schacon/blink <1>
+-
+-$ git fetch upstream <2>
+-remote: Counting objects: 3, done.
+-remote: Compressing objects: 100% (3/3), done.
+-Unpacking objects: 100% (3/3), done.
+-remote: Total 3 (delta 0), reused 0 (delta 0)
+-From https://github.com/schacon/blink
+- * [new branch]      master     -> upstream/master
+-
+-$ git merge upstream/master <3>
+-Auto-merging blink.ino
+-CONFLICT (content): Merge conflict in blink.ino
+-Automatic merge failed; fix conflicts and then commit the result.
+-
+-$ vim blink.ino <4>
+-$ git add blink.ino
+-$ git commit
+-[slow-blink 3c8d735] Merge remote-tracking branch 'upstream/master' \
+-    into slower-blink
+-
+-$ git push origin slow-blink <5>
+-Counting objects: 6, done.
+-Delta compression using up to 8 threads.
+-Compressing objects: 100% (6/6), done.
+-Writing objects: 100% (6/6), 682 bytes | 0 bytes/s, done.
+-Total 6 (delta 2), reused 0 (delta 0)
+-To https://github.com/tonychacon/blink
+-   ef4725c..3c8d735  slower-blink -> slow-blink
+-----
+-
+-<1> Add the original repository as a remote named `upstream`.
+-<2> Fetch the newest work from that remote.
+-<3> Merge the main branch of that repository into your topic branch.
+-<4> Fix the conflict that occurred.
+-<5> Push back up to the same topic branch.
++<1> Add the original repository as a remote named ``upstream''
++<2> Fetch the newest work from that remote
++<3> Merge the main branch into your topic branch
++<4> Fix the conflict that occurred
++<5> Push back up to the same topic branch
+ 
+ Once you do that, the Pull Request will be automatically updated and re-checked to see if it merges cleanly.
+ 
+-[[_pr_merge_fix]]
+ .Pull Request now merges cleanly
+ image::images/pr-02-merge-fix.png[PR fixed]
+ 
+-One of the great things about Git is that you can do that continuously.
+-If you have a very long-running project, you can easily merge from the target branch over and over again and only have to deal with conflicts that have arisen since the last time that you merged, making the process very manageable.
++One of the great things about Git is that you can do that continuously. If you have a very long-running project, you can easily merge from the target branch over and over again and only have to deal with conflicts that have arisen since the last time that you merged, making the process very manageable.
+ 
+-If you absolutely wish to rebase the branch to clean it up, you can certainly do so, but it is highly encouraged to not force push over the branch that the Pull Request is already opened on.
+-If other people have pulled it down and done more work on it, you run into all of the issues outlined in <<ch03-git-branching#_rebase_peril>>.
+-Instead, push the rebased branch to a new branch on GitHub and open a brand new Pull Request referencing the old one, then close the original.
++If you absolutely wish to rebase the branch to clean it up, you can certainly do so, but it is highly encouraged to not force push over the branch that the Pull Request is already opened on. If other people have pulled it down and done more work on it, you run into all of the issues outlined in <<ch03-git-branching#r_rebase_peril>>. Instead, push the rebased branch to a new branch on GitHub and open a brand new Pull Request referencing the old one, then close the original.
+ 
+ ===== References
+ 
+-Your next question may be ``How do I reference the old Pull Request?''.
+-It turns out there are many, many ways to reference other things almost anywhere you can write in GitHub.
++Your next question may be ``How do I reference the old Pull Request?''. It turns out there are many, many ways to reference other things almost anywhere you can write in GitHub.
+ 
+-Let's start with how to cross-reference another Pull Request or an Issue.
+-All Pull Requests and Issues are assigned numbers and they are unique within the project.
+-For example, you can't have Pull Request #3 _and_ Issue #3.
+-If you want to reference any Pull Request or Issue from any other one, you can simply put `#<num>` in any comment or description.
+-You can also be more specific if the Issue or Pull request lives somewhere else; write `username#<num>` if you're referring to an Issue or Pull Request in a fork of the repository you're in, or `username/repo#<num>` to reference something in another repository.
+-
+-Let's look at an example.
+-Say we rebased the branch in the previous example, created a new pull request for it, and now we want to reference the old pull request from the new one.
+-We also want to reference an issue in the fork of the repository and an issue in a completely different project.
+-We can fill out the description just like <<_pr_references>>.
++Let's start with how to cross-reference another Pull Request or an Issue. All Pull Requests and Issues are assigned numbers and they are unique within the project. For example, you can't have Pull Request #3 _and_ Issue #3. If you want to reference any Pull Request or Issue from any other one, you can simply put `#<num>` in any comment or description. You can also be more specific if the Issue or Pull request lives somewhere else; write `username#<num>` if you're referring to an Issue or Pull Request in a fork of the repository you're in, or `username/repo#<num>` to reference something in another repository.
+ 
+-[[_pr_references]]
+-.Cross references in a Pull Request
++Let's look at an example. Say we rebased the branch in the previous example, created a new pull request for it, and now we want to reference the old pull request from the new one. We also want to reference an issue in the fork of the repository and an issue in a completely different project. We can fill out the description just like <<r_pr_references>>.
++
++.Cross references in a Pull Request.
+ image::images/mentions-01-syntax.png[PR references]
+ 
+-When we submit this pull request, we'll see all of that rendered like <<_pr_references_render>>.
++When we submit this pull request, we'll see all of that rendered like <<r_pr_references_render>>.
+ 
+-[[_pr_references_render]]
+-.Cross references rendered in a Pull Request
++.Cross references rendered in a Pull Request.
+ image::images/mentions-02-render.png[PR references rendered]
+ 
+ Notice that the full GitHub URL we put in there was shortened to just the information needed.
+ 
+-Now if Tony goes back and closes out the original Pull Request, we can see that by mentioning it in the new one, GitHub has automatically created a trackback event in the Pull Request timeline.
+-This means that anyone who visits this Pull Request and sees that it is closed can easily link back to the one that superseded it.
+-The link will look something like <<_pr_closed>>.
++Now if Tony goes back and closes out the original Pull Request, we can see that by mentioning it in the new one, GitHub has automatically created a trackback event in the Pull Request timeline. This means that anyone who visits this Pull Request and sees that it is closed can easily link back to the one that superseded it. The link will look something like <<r_pr_closed>>.
+ 
+-[[_pr_closed]]
+-.Link back to the new Pull Request in the closed Pull Request timeline
++.Cross references rendered in a Pull Request.
+ image::images/mentions-03-closed.png[PR closed]
+ 
+-In addition to issue numbers, you can also reference a specific commit by SHA-1.
+-You have to specify a full 40 character SHA-1, but if GitHub sees that in a comment, it will link directly to the commit.
+-Again, you can reference commits in forks or other repositories in the same way you did with issues.
++In addition to issue numbers, you can also reference a specific commit by SHA-1. You have to specify a full 40 character SHA-1, but if GitHub sees that in a comment, it will link directly to the commit. Again, you can reference commits in forks or other repositories in the same way you did with issues.
+ 
+-==== GitHub Flavored Markdown
++==== Markdown
+ 
+-Linking to other Issues is just the beginning of interesting things you can do with almost any text box on GitHub.
+-In  Issue and Pull Request descriptions, comments, code comments and more, you can use what is called ``GitHub Flavored Markdown''.
+-Markdown is like writing in plain text but which is rendered richly.
++Linking to other Issues is just the beginning of interesting things you can do with almost any text box on GitHub. In  Issue and Pull Request descriptions, comments, code comments and more, you can use what is called ``GitHub Flavored Markdown''. Markdown is like writing in plain text but which is rendered richly.
+ 
+-See <<_example_markdown>> for an example of how comments or text can be written and then rendered using Markdown.
++See <<r_example_markdown>> for an example of how comments or text can be written and then rendered using Markdown.
+ 
+-[[_example_markdown]]
+-.An example of GitHub Flavored Markdown as written and as rendered
++.An example of Markdown as written and as rendered.
+ image::images/markdown-01-example.png[Example Markdown]
+ 
+-The GitHub flavor of Markdown adds more things you can do beyond the basic Markdown syntax.
+-These can all be really useful when creating useful Pull Request or Issue comments or descriptions.
++===== GitHub Flavored Markdown
+ 
+-===== Task Lists
++The GitHub flavor of Markdown adds more things you can do beyond the basic Markdown syntax. These can all be really useful when creating useful Pull Request or Issue comments or descriptions.
+ 
+-The first really useful GitHub specific Markdown feature, especially for use in Pull Requests, is the Task List.
+-A task list is a list of checkboxes of things you want to get done.
+-Putting them into an Issue or Pull Request normally indicates things that you want to get done before you consider the item complete.
++====== Task Lists
+ 
+-You can create a task list like this:
++The first really useful GitHub specific Markdown feature, especially for use in Pull Requests, is the Task List. A task list is a list of checkboxes of things you want to get done. Putting them into an Issue or Pull Request normally indicates things that you want to get done before you consider the item complete.
+ 
+-[source,text]
+-----
+-- [X] Write the code
+-- [ ] Write all the tests
+-- [ ] Document the code
+-----
++You can create a task list like this:
+ 
+-If we include this in the description of our Pull Request or Issue, we'll see it rendered like <<_eg_task_lists>>.
++If we include this in the description of our Pull Request or Issue, we'll see it rendered like <<r_task_lists>>
+ 
+-[[_eg_task_lists]]
+-.Task lists rendered in a Markdown comment
++.Task lists rendered in a Markdown comment.
+ image::images/markdown-02-tasks.png[Example Task List]
+ 
+-This is often used in Pull Requests to indicate what all you would like to get done on the branch before the Pull Request will be ready to merge.
+-The really cool part is that you can simply click the checkboxes to update the comment -- you don't have to edit the Markdown directly to check tasks off.
++This is often used in Pull Requests to indicate what all you would like to get done on the branch before the Pull Request will be ready to merge. The really cool part is that you can simply click the checkboxes to update the comment -- you don't have to edit the Markdown directly to check tasks off.
+ 
+-What's more, GitHub will look for task lists in your Issues and Pull Requests and show them as metadata on the pages that list them out.
+-For example, if you have a Pull Request with tasks and you look at the overview page of all Pull Requests, you can see how far done it is.
+-This helps people break down Pull Requests into subtasks and helps other people track the progress of the branch.
+-You can see an example of this in <<_task_list_progress>>.
++What's more, GitHub will look for task lists in your Issues and Pull Requests and show them as metadata on the pages that list them out. For example, if you have a Pull Request with tasks and you look at the overview page of all Pull Requests, you can see how far done it is. This helps people break down Pull Requests into subtasks and helps other people track the progress of the branch. You can see an example of this in <<r_task_list_progress>>.
+ 
+-[[_task_list_progress]]
+-.Task list summary in the Pull Request list
++.Task list summary in the Pull Request list.
+ image::images/markdown-03-task-summary.png[Example Task List]
+ 
+ These are incredibly useful when you open a Pull Request early and use it to track your progress through the implementation of the feature.
+ 
+-===== Code Snippets
++====== Code Snippets
+ 
+-You can also add code snippets to comments.
+-This is especially useful if you want to present something that you _could_ try to do before actually implementing it as a commit on your branch.
+-This is also often used to add example code of what is not working or what this Pull Request could implement.
++You can also add code snippets to comments. This is especially useful if you want to present something that you _could_ try to do before actually implementing it as a commit on your branch. This is also often used to add example code of what is not working or what this Pull Request could implement.
+ 
+ To add a snippet of code you have to ``fence'' it in backticks.
+ 
+-[source,text]
+-----
+-```java
+-for(int i=0 ; i < 5 ; i++)
+-{
+-   System.out.println("i is : " + i);
+-}
+-```
+-----
++If you add a language name like we did there with 'java', GitHub will also try to syntax highlight the snippet. In the case of the above example, it would end up rendering like <<r_md_code>>.
+ 
+-If you add a language name like we did there with 'java', GitHub will also try to syntax highlight the snippet.
+-In the case of the above example, it would end up rendering like <<_md_code>>.
+-
+-[[_md_code]]
+-.Rendered fenced code example
++.Rendered fenced code example.
+ image::images/markdown-04-fenced-code.png[Rendered fenced code]
+ 
+-===== Quoting
++====== Quoting
+ 
+-If you're responding to a small part of a long comment, you can selectively quote out of the other comment by preceding the lines with the `>` character.
+-In fact, this is so common and so useful that there is a keyboard shortcut for it.
+-If you highlight text in a comment that you want to directly reply to and hit the `r` key, it will quote that text in the comment box for you.
++If you're responding to a small part of a long comment, you can selectively quote out of the other comment by preceding the lines with the `>` character. In fact, this is so common and so useful that there is a keyboard shortcut for it. If you highlight text in a comment that you want to directly reply to and hit the `r` key, it will quote that text in the comment box for you.
+ 
+ The quotes look something like this:
+ 
+-[source,text]
+-----
+-> Whether 'tis Nobler in the mind to suffer
+-> The Slings and Arrows of outrageous Fortune,
+-
+-How big are these slings and in particular, these arrows?
+-----
++Once rendered, the comment will look like <<r_md_quote>>.
+ 
+-Once rendered, the comment will look like <<_md_quote>>.
+-
+-[[_md_quote]]
+-.Rendered quoting example
++.Rendered quoting example.
+ image::images/markdown-05-quote.png[Rendered quoting]
+ 
+-===== Emoji
++====== Emoji
+ 
+-Finally, you can also use emoji in your comments.
+-This is actually used quite extensively in comments you see on many GitHub Issues and Pull Requests.
+-There is even an emoji helper in GitHub.
+-If you are typing a comment and you start with a `:` character, an autocompleter will help you find what you're looking for.
++Finally, you can also use emoji in your comments. This is actually used quite extensively in comments you see on many GitHub Issues and Pull Requests. There is even an emoji helper in GitHub. If you are typing a comment and you start with a `:` character, an autocompleter will help you find what you're looking for.
+ 
+-[[_md_emoji_auto]]
+-.Emoji autocompleter in action
++.Emoji autocompleter in action.
+ image::images/markdown-06-emoji-complete.png[Emoji autocompleter]
+ 
+-Emojis take the form of `:<name>:` anywhere in the comment.
+-For instance, you could write something like this:
+-
+-[source,text]
+-----
+-I :eyes: that :bug: and I :cold_sweat:.
+-
+-:trophy: for :microscope: it.
+-
+-:+1: and :sparkles: on this :ship:, it's :fire::poop:!
+-
+-:clap::tada::panda_face:
+-----
++Emojis take the form of `:<name>:` anywhere in the comment. For instance, you could write something like this:
+ 
+-When rendered, it would look something like <<_md_emoji>>.
++When rendered, it would look something like <<r_md_emoji>>.
+ 
+-[[_md_emoji]]
+-.Heavy emoji commenting
++.Heavy emoji commenting.
+ image::images/markdown-07-emoji.png[Emoji]
+ 
+ Not that this is incredibly useful, but it does add an element of fun and emotion to a medium that is otherwise hard to convey emotion in.
+ 
+-
+-[NOTE]
+ ====
+-There are actually quite a number of web services that make use of emoji characters these days.
+-A great cheat sheet to reference to find emoji that expresses what you want to say can be found at:
++There are actually quite a number of web services that make use of emoji characters these days. A great cheat sheet to reference to find emoji that expresses what you want to say can be found at:
+ 
+-https://www.webfx.com/tools/emoji-cheat-sheet/
++http://www.emoji-cheat-sheet.com
+ ====
+ 
+-===== Images
++====== Images
+ 
+-This isn't technically GitHub Flavored Markdown, but it is incredibly useful.
+-In addition to adding Markdown image links to comments, which can be difficult to find and embed URLs for, GitHub allows you to drag and drop images into text areas to embed them.
++This isn't technically GitHub Flavored Markdown, but it is incredibly useful. In addition to adding Markdown image links to comments, which can be difficult to find and embed URLs for, GitHub allows you to drag and drop images into text areas to embed them.
+ 
+-[[_md_drag]]
+-.Drag and drop images to upload them and auto-embed them
++.Drag and drop images to upload them and auto-embed them.
+ image::images/markdown-08-drag-drop.png[Drag and drop images]
+ 
+-If you look at <<_md_drag>>, you can see a small ``Parsed as Markdown'' hint above the text area.
+-Clicking on that will give you a full cheat sheet of everything you can do with Markdown on GitHub.
+-
+-[[_fetch_and_push_on_different_repositories]]
+-==== Keep your GitHub public repository up-to-date
+-
+-Once you've forked a GitHub repository, your repository (your "fork") exists independently from the original.
+-In particular, when the original repository has new commits, GitHub informs you by a message like:
+-
+-[source,text]
+-----
+-This branch is 5 commits behind progit:master.
+-----
+-
+-But your GitHub repository will never be automatically updated by GitHub; this is something that you must do yourself.
+-Fortunately, this is very easy to do.
+-
+-One possibility to do this requires no configuration.
+-For example, if you forked from `https://github.com/progit/progit2.git`, you can keep your `master` branch up-to-date like this:
+-
+-[source,console]
+-----
+-$ git checkout master <1>
+-$ git pull https://github.com/progit/progit2.git <2>
+-$ git push origin master <3>
+-----
+-
+-<1> If you were on another branch, return to `master`.
+-<2> Fetch changes from `https://github.com/progit/progit2.git` and merge them into `master`.
+-<3> Push your `master` branch to `origin`.
+-
+-This works, but it is a little tedious having to spell out the fetch URL every time.
+-You can automate this work with a bit of configuration:
+-
+-[source,console]
+-----
+-$ git remote add progit https://github.com/progit/progit2.git <1>
+-$ git branch --set-upstream-to=progit/master master <2>
+-$ git config --local remote.pushDefault origin <3>
+-----
+-
+-<1> Add the source repository and give it a name.
+-    Here, I have chosen to call it `progit`.
+-<2> Set your `master` branch to fetch from the `progit` remote.
+-<3> Define the default push repository to `origin`.
+-
+-Once this is done, the workflow becomes much simpler:
+-
+-[source,console]
+-----
+-$ git checkout master <1>
+-$ git pull <2>
+-$ git push <3>
+-----
+-
+-<1> If you were on another branch, return to `master`.
+-<2> Fetch changes from `progit` and merge changes into `master`.
+-<3> Push your `master` branch to `origin`.
+-
+-This approach can be useful, but it's not without downsides.
+-Git will happily do this work for you silently, but it won't warn you if you make a commit to `master`, pull from `progit`, then push to `origin` -- all of those operations are valid with this setup.
+-So you'll have to take care never to commit directly to `master`, since that branch effectively belongs to the upstream repository.
++If you look back at <<r_pr_references>>, you can see a small ``Parsed as Markdown'' hint above the text area. Clicking on that will give you a full cheat sheet of everything you can do with Markdown on GitHub.
+diff -au ../../git/progit2/progit2/book/06-github/sections/3-maintaining.asc /tmp/book/06-github/sections/3-maintaining.asc.tmp
+--- ../../git/progit2/progit2/book/06-github/sections/3-maintaining.asc	2020-07-04 16:36:46.732685561 +0900
++++ /tmp/book/06-github/sections/3-maintaining.asc.tmp	2020-10-25 09:24:25.777972418 +0900
+@@ -1,4 +1,4 @@
+-[[_maintaining_gh_project]]
++[[r_maintaining_gh_project]]
+ === Maintaining a Project
+ 
+ Now that we're comfortable contributing to a project, let's look at the other side: creating, maintaining and administering your own project.
+@@ -6,35 +6,33 @@
+ ==== Creating a New Repository
+ 
+ Let's create a new repository to share our project code with.
+-Start by clicking the ``New repository'' button on the right-hand side of the dashboard, or from the `+` button in the top toolbar next to your username as seen in <<_new_repo_dropdown>>.
++Start by clicking the ``New repository'' button on the right-hand side of the dashboard, or from the `+` button in the top toolbar next to your username as seen in <<r_new_repo_dropdown>>.
+ 
+-.The ``Your repositories'' area
+-image::images/newrepo.png[The ``Your repositories'' area]
++.The ``Your repositories'' area.
++image::images/newrepo.png[The ``Your repositories'' area.]
+ 
+-[[_new_repo_dropdown]]
+-.The ``New repository'' dropdown
+-image::images/new-repo.png[The ``new repository'' dropdown]
++.The ``New repository'' dropdown.
++image::images/new-repo.png[The ``new repository'' dropdown.]
+ 
+ This takes you to the ``new repository'' form:
+ 
+-.The ``new repository'' form
+-image::images/newrepoform.png[The ``new repository'' form]
++.The ``new repository'' form.
++image::images/newrepoform.png[The ``new repository'' form.]
+ 
+ All you really have to do here is provide a project name; the rest of the fields are completely optional.
+ For now, just click the ``Create Repository'' button, and boom – you have a new repository on GitHub, named `<user>/<project_name>`.
+ 
+ Since you have no code there yet, GitHub will show you instructions for how to create a brand-new Git repository, or connect an existing Git project.
+-We won't belabor this here; if you need a refresher, check out <<ch02-git-basics-chapter#ch02-git-basics-chapter>>.
++We won't belabor this here; if you need a refresher, check out <<ch02-git-basics#ch02-git-basics>>.
+ 
+ Now that your project is hosted on GitHub, you can give the URL to anyone you want to share your project with.
+-Every project on GitHub is accessible over HTTPS as `https://github.com/<user>/<project_name>`, and over SSH as `[e-mail]:<user>/<project_name>`.
++Every project on GitHub is accessible over HTTP as `https://github.com/<user>/<project_name>`, and over SSH as `[e-mail]:<user>/<project_name>`.
+ Git can fetch from and push to both of these URLs, but they are access-controlled based on the credentials of the user connecting to them.
+ 
+-[NOTE]
+ ====
+-It is often preferable to share the HTTPS based URL for a public project, since the user does not have to have a GitHub account to access it for cloning.
++It is often preferable to share the HTTP based URL for a public project, since the user does not have to have a GitHub account to access it for cloning.
+ Users will have to have an account and an uploaded SSH key to access your project if you give them the SSH URL.
+-The HTTPS one is also exactly the same URL they would paste into a browser to view the project there.
++The HTTP one is also exactly the same URL they would paste into a browser to view the project there.
+ ====
+ 
+ ==== Adding Collaborators
+@@ -45,16 +43,16 @@
+ 
+ Click the ``Settings'' link at the bottom of the right-hand sidebar.
+ 
+-.The repository settings link
+-image::images/reposettingslink.png[The repository settings link]
++.The repository settings link.
++image::images/reposettingslink.png[The repository settings link.]
+ 
+ Then select ``Collaborators'' from the menu on the left-hand side.
+ Then, just type a username into the box, and click ``Add collaborator.''
+ You can repeat this as many times as you like to grant access to everyone you like.
+ If you need to revoke access, just click the ``X'' on the right-hand side of their row.
+ 
+-.Repository collaborators
+-image::images/collaborators.png[The repository collaborators box]
++.Repository collaborators.
++image::images/collaborators.png[The repository collaborators box.]
+ 
+ ==== Managing Pull Requests
+ 
+@@ -65,14 +63,12 @@
+ 
+ For these examples, let's assume you are ``tonychacon'' and you've created a new Arduino code project named ``fade''.
+ 
+-[[_email_notifications]]
+ ===== Email Notifications
+ 
+ Someone comes along and makes a change to your code and sends you a Pull Request.
+-You should get an email notifying you about the new Pull Request and it should look something like <<_email_pr>>.
++You should get an email notifying you about the new Pull Request and it should look something like <<r_email_pr>>.
+ 
+-[[_email_pr]]
+-.Email notification of a new Pull Request
++.Email notification of a new Pull Request.
+ image::images/maint-01-email.png[Pull Request email notification]
+ 
+ There are a few things to notice about this email.
+@@ -81,26 +77,21 @@
+ It also gives you a few URLs that you can use from the command line.
+ 
+ If you notice the line that says `git pull <url> patch-1`, this is a simple way to merge in a remote branch without having to add a remote.
+-We went over this quickly in <<ch05-distributed-git#_checking_out_remotes>>.
++We went over this quickly in <<ch05-distributed-git#r_checking_out_remotes>>.
+ If you wish, you can create and switch to a topic branch and then run this command to merge in the Pull Request changes.
+ 
+ The other interesting URLs are the `.diff` and `.patch` URLs, which as you may guess, provide unified diff and patch versions of the Pull Request.
+ You could technically merge in the Pull Request work with something like this:
+ 
+-[source,console]
+-----
+-$ curl https://github.com/tonychacon/fade/pull/1.patch | git am
+-----
+-
+ ===== Collaborating on the Pull Request
+ 
+-As we covered in <<ch06-github#ch06-github_flow>>, you can now have a conversation with the person who opened the Pull Request.
++As we covered in <<r_github_flow>>, you can now have a conversation with the person who opened the Pull Request.
+ You can comment on specific lines of code, comment on whole commits or comment on the entire Pull Request itself, using GitHub Flavored Markdown everywhere.
+ 
+ Every time someone else comments on the Pull Request you will continue to get email notifications so you know there is activity happening.
+ They will each have a link to the Pull Request where the activity is happening and you can also directly respond to the email to comment on the Pull Request thread.
+ 
+-.Responses to emails are included in the thread
++.Responses to emails are included in the thread.
+ image::images/maint-03-email-resp.png[Email response]
+ 
+ Once the code is in a place you like and want to merge it in, you can either pull the code down and merge it locally, either with the `git pull <url> <branch>` syntax we saw earlier, or by adding the fork as a remote and fetching and merging.
+@@ -108,41 +99,26 @@
+ If the merge is trivial, you can also just hit the ``Merge'' button on the GitHub site.
+ This will do a ``non-fast-forward'' merge, creating a merge commit even if a fast-forward merge was possible.
+ This means that no matter what, every time you hit the merge button, a merge commit is created.
+-As you can see in <<_merge_button>>, GitHub gives you all of this information if you click the hint link.
++As you can see in <<r_merge_button>>, GitHub gives you all of this information if you click the hint link.
+ 
+-[[_merge_button]]
+-.Merge button and instructions for merging a Pull Request manually
++.Merge button and instructions for merging a Pull Request manually.
+ image::images/maint-02-merge.png[Merge button]
+ 
+ If you decide you don't want to merge it, you can also just close the Pull Request and the person who opened it will be notified.
+ 
+-[[_pr_refs]]
+ ===== Pull Request Refs
+ 
+ If you're dealing with a *lot* of Pull Requests and don't want to add a bunch of remotes or do one time pulls every time, there is a neat trick that GitHub allows you to do.
+-This is a bit of an advanced trick and we'll go over the details of this a bit more in <<ch10-git-internals#_refspec>>, but it can be pretty useful.
++This is a bit of an advanced trick and we'll go over the details of this a bit more in <<ch10-git-internals#r_refspec>>, but it can be pretty useful.
+ 
+ GitHub actually advertises the Pull Request branches for a repository as sort of pseudo-branches on the server.
+ By default you don't get them when you clone, but they are there in an obscured way and you can access them pretty easily.
+ 
+-To demonstrate this, we're going to use a low-level command (often referred to as a ``plumbing'' command, which we'll read about more in <<ch10-git-internals#_plumbing_porcelain>>) called `ls-remote`.
++To demonstrate this, we're going to use a low-level command (often referred to as a ``plumbing'' command, which we'll read about more in <<ch10-git-internals#r_plumbing_porcelain>>) called `ls-remote`.
+ This command is generally not used in day-to-day Git operations but it's useful to show us what references are present on the server.
+ 
+ If we run this command against the ``blink'' repository we were using earlier, we will get a list of all the branches and tags and other references in the repository.
+ 
+-[source,console]
+-----
+-$ git ls-remote https://github.com/schacon/blink
+-10d539600d86723087810ec636870a504f4fee4d	HEAD
+-10d539600d86723087810ec636870a504f4fee4d	refs/heads/master
+-6a83107c62950be9453aac297bb0193fd743cd6e	refs/pull/1/head
+-afe83c2d1a70674c9505cc1d8b7d380d5e076ed3	refs/pull/1/merge
+-3c8d735ee16296c242be7a9742ebfbc2665adec1	refs/pull/2/head
+-15c9f4f80973a2758462ab2066b6ad9fe8dcf03d	refs/pull/2/merge
+-a5a7751a33b7e86c5e9bb07b26001bb17d775d1a	refs/pull/4/head
+-31a45fc257e8433c8d8804e3e848cf61c9d3166c	refs/pull/4/merge
+-----
+-
+ Of course, if you're in your repository and you run `git ls-remote origin` or whatever remote you want to check, it will show you something similar to this.
+ 
+ If the repository is on GitHub and you have any Pull Requests that have been opened, you'll get these references that are prefixed with `refs/pull/`.
+@@ -154,13 +130,6 @@
+ 
+ Now, you could do something like fetching the reference directly.
+ 
+-[source,console]
+-----
+-$ git fetch origin refs/pull/958/head
+-From https://github.com/libgit2/libgit2
+- * branch            refs/pull/958/head -> FETCH_HEAD
+-----
+-
+ This tells Git, ``Connect to the `origin` remote, and download the ref named `refs/pull/958/head`.''
+ Git happily obeys, and downloads everything you need to construct that ref, and puts a pointer to the commit you want under `.git/FETCH_HEAD`.
+ You can follow that up with `git merge FETCH_HEAD` into a branch you want to test it in, but that merge commit message looks a bit weird.
+@@ -170,55 +139,21 @@
+ Open up `.git/config` in your favorite editor, and look for the `origin` remote.
+ It should look a bit like this:
+ 
+-[source,ini]
+-----
+-[remote "origin"]
+-    url = https://github.com/libgit2/libgit2
+-    fetch = +refs/heads/*:refs/remotes/origin/*
+-----
+-
+ That line that begins with `fetch =` is a ``refspec.''
+ It's a way of mapping names on the remote with names in your local `.git` directory.
+ This particular one tells Git, "the things on the remote that are under `refs/heads` should go in my local repository under `refs/remotes/origin`."
+ You can modify this section to add another refspec:
+ 
+-[source,ini]
+-----
+-[remote "origin"]
+-    url = https://github.com/libgit2/libgit2.git
+-    fetch = +refs/heads/*:refs/remotes/origin/*
+-    fetch = +refs/pull/*/head:refs/remotes/origin/pr/*
+-----
+-
+ That last line tells Git, ``All the refs that look like `refs/pull/123/head` should be stored locally like `refs/remotes/origin/pr/123`.''
+ Now, if you save that file, and do a `git fetch`:
+ 
+-[source,console]
+-----
+-$ git fetch
+-# …
+- * [new ref]         refs/pull/1/head -> origin/pr/1
+- * [new ref]         refs/pull/2/head -> origin/pr/2
+- * [new ref]         refs/pull/4/head -> origin/pr/4
+-# …
+-----
+-
+ Now all of the remote pull requests are represented locally with refs that act much like tracking branches; they're read-only, and they update when you do a fetch.
+ This makes it super easy to try the code from a pull request locally:
+ 
+-[source,console]
+-----
+-$ git checkout pr/2
+-Checking out files: 100% (3769/3769), done.
+-Branch pr/2 set up to track remote branch pr/2 from origin.
+-Switched to a new branch 'pr/2'
+-----
+-
+ The eagle-eyed among you would note the `head` on the end of the remote portion of the refspec.
+ There's also a `refs/pull/#/merge` ref on the GitHub side, which represents the commit that would result if you push the ``merge'' button on the site.
+ This can allow you to test the merge before even hitting the button.
+ 
+-
+ ===== Pull Requests on Pull Requests
+ 
+ Not only can you open Pull Requests that target the main or `master` branch, you can actually open a Pull Request targeting any branch in the network.
+@@ -229,8 +164,7 @@
+ When you go to open a Pull Request, there is a box at the top of the page that specifies which branch you're requesting to pull to and which you're requesting to pull from.
+ If you hit the ``Edit'' button at the right of that box you can change not only the branches but also which fork.
+ 
+-[[_pr_targets]]
+-.Manually change the Pull Request target fork and branch
++.Manually change the Pull Request target fork and branch.
+ image::images/maint-04-target.png[PR targets]
+ 
+ Here you can fairly easily specify to merge your new branch into another Pull Request or another fork of the project.
+@@ -241,7 +175,7 @@
+ 
+ In any comment you can start typing a `@` character and it will begin to autocomplete with the names and usernames of people who are collaborators or contributors in the project.
+ 
+-.Start typing @ to mention someone
++.Start typing @ to mention someone.
+ image::images/maint-05-mentions.png[Mentions]
+ 
+ You can also mention a user who is not in that dropdown, but often the autocompleter can make it faster.
+@@ -254,7 +188,7 @@
+ You will also be subscribed to something if you opened it, if you're watching the repository or if you comment on something.
+ If you no longer wish to receive notifications, there is an ``Unsubscribe'' button on the page you can click to stop receiving updates on it.
+ 
+-.Unsubscribe from an Issue or Pull Request
++.Unsubscribe from an Issue or Pull Request.
+ image::images/maint-06-unsubscribe.png[Unsubscribe]
+ 
+ ===== The Notifications Page
+@@ -262,7 +196,7 @@
+ When we mention ``notifications'' here with respect to GitHub, we mean a specific way that GitHub tries to get in touch with you when events happen and there are a few different ways you can configure them.
+ If you go to the ``Notification center'' tab from the settings page, you can see some of the options you have.
+ 
+-.Notification center options
++.Notification center options.
+ image::images/maint-07-notifications.png[Notification center]
+ 
+ The two choices are to get notifications over ``Email'' and over ``Web'' and you can choose either, neither or both for when you actively participate in things and for activity on repositories you are watching.
+@@ -270,10 +204,9 @@
+ ====== Web Notifications
+ 
+ Web notifications only exist on GitHub and you can only check them on GitHub.
+-If you have this option selected in your preferences and a notification is triggered for you, you will see a small blue dot over your notifications icon at the top of your screen as seen in <<_not_center>>.
++If you have this option selected in your preferences and a notification is triggered for you, you will see a small blue dot over your notifications icon at the top of your screen as seen in <<r_not_center>>.
+ 
+-[[_not_center]]
+-.Notification center
++.Notification center.
+ image::images/maint-08-notifications-page.png[Notification center]
+ 
+ If you click on that, you will see a list of all the items you have been notified about, grouped by project.
+@@ -288,25 +221,12 @@
+ 
+ Email notifications are the other way you can handle notifications through GitHub.
+ If you have this turned on you will get emails for each notification.
+-We saw examples of this in <<_email_notification>> and <<_email_pr>>.
++We saw examples of this in <<r_email_notification>> and <<r_email_pr>>.
+ The emails will also be threaded properly, which is nice if you're using a threading email client.
+ 
+ There is also a fair amount of metadata embedded in the headers of the emails that GitHub sends you, which can be really helpful for setting up custom filters and rules.
+ 
+-For instance, if we look at the actual email headers sent to Tony in the email shown in <<_email_pr>>, we will see the following among the information sent:
+-
+-[source,mbox]
+-----
+-To: tonychacon/fade <[e-mail]>
+-Message-ID: <tonychacon/fade/pull/[e-mail]>
+-Subject: [fade] Wait longer to see the dimming effect better (#1)
+-X-GitHub-Recipient: tonychacon
+-List-ID: tonychacon/fade <fade.tonychacon.github.com>
+-List-Archive: https://github.com/tonychacon/fade
+-List-Post: <mailto:[e-mail]>
+-List-Unsubscribe: <mailto:[e-mail]>,...
+-X-GitHub-Recipient-Address: [e-mail]
+-----
++For instance, if we look at the actual email headers sent to Tony in the email shown in <<r_email_pr>>, we will see the following among the information sent:
+ 
+ There are a couple of interesting things here.
+ If you want to highlight or re-route emails to this particular project or even Pull Request, the information in `Message-ID` gives you all the data in `<user>/<project>/<type>/<id>` format.
+@@ -321,8 +241,6 @@
+ 
+ There are a couple of special files that GitHub will notice if they are present in your repository.
+ 
+-==== README
+-
+ The first is the `README` file, which can be of nearly any format that GitHub recognizes as prose.
+ For example, it could be `README`, `README.md`, `README.asciidoc`, etc.
+ If GitHub sees a README file in your source, it will render it on the landing page of the project.
+@@ -338,13 +256,10 @@
+ 
+ Since GitHub will render this file, you can embed images or links in it for added ease of understanding.
+ 
+-==== CONTRIBUTING
+-
+ The other special file that GitHub recognizes is the `CONTRIBUTING` file.
+-If you have a file named `CONTRIBUTING` with any file extension, GitHub will show <<_contrib_file>> when anyone starts opening a Pull Request.
++If you have a file named `CONTRIBUTING` with any file extension, GitHub will show <<r_contrib_file>> when anyone starts opening a Pull Request.
+ 
+-[[_contrib_file]]
+-.Opening a Pull Request when a CONTRIBUTING file exists
++.Opening a Pull Request when a CONTRIBUTING file exists.
+ image::images/maint-09-contrib.png[Contributing notice]
+ 
+ The idea here is that you can specify specific things you want or don't want in a Pull Request sent to your project.
+@@ -358,8 +273,7 @@
+ 
+ If you are using a branch other than ``master'' as your default branch that you want people to open Pull Requests on or see by default, you can change that in your repository's settings page under the ``Options'' tab.
+ 
+-[[_default_branch]]
+-.Change the default branch for a project
++.Change the default branch for a project.
+ image::images/maint-10-default-branch.png[Default branch]
+ 
+ Simply change the default branch in the dropdown and that will be the default for all major operations from then on, including which branch is checked out by default when someone clones the repository.
+@@ -368,8 +282,7 @@
+ 
+ If you would like to transfer a project to another user or an organization in GitHub, there is a ``Transfer ownership'' option at the bottom of the same ``Options'' tab of your repository settings page that allows you to do this.
+ 
+-[[_transfer_project]]
+-.Transfer a project to another GitHub user or Organization
++.Transfer a project to another GitHub user or Organization.
+ image::images/maint-11-transfer.png[Transfer]
+ 
+ This is helpful if you are abandoning a project and someone wants to take it over, or if your project is getting bigger and want to move it into an organization.
+diff -au ../../git/progit2/progit2/book/06-github/sections/4-managing-organization.asc /tmp/book/06-github/sections/4-managing-organization.asc.tmp
+--- ../../git/progit2/progit2/book/06-github/sections/4-managing-organization.asc	2020-07-04 16:36:46.732685561 +0900
++++ /tmp/book/06-github/sections/4-managing-organization.asc.tmp	2020-10-25 09:24:25.783972701 +0900
+@@ -1,7 +1,6 @@
+-[[ch06-github_orgs]]
++[[r_github_orgs]]
+ === Managing an organization
+ 
+-(((GitHub, organizations)))
+ In addition to single-user accounts, GitHub has what are called Organizations.
+ Like personal accounts, Organizational accounts have a namespace where all their projects exist, but many other things are different.
+ These accounts represent a group of people with shared ownership of projects, and there are many tools to manage subgroups of those people.
+@@ -11,8 +10,8 @@
+ 
+ An organization is pretty easy to create; just click on the ``+'' icon at the top-right of any GitHub page, and select ``New organization'' from the menu.
+ 
+-.The ``New organization'' menu item
+-image::images/neworg.png[The ``New organization'' menu item]
++.The ``New organization'' menu item.
++image::images/neworg.png[The ``New organization'' menu item.]
+ 
+ First you'll need to name your organization and provide an email address for a main point of contact for the group.
+ Then you can invite other users to be co-owners of the account if you want to.
+@@ -24,7 +23,7 @@
+ When you create new repositories you can create them either under your personal account or under any of the organizations that you are an owner in.
+ You also automatically ``watch'' any new repository created under these organizations.
+ 
+-Just like in <<_personal_avatar>>, you can upload an avatar for your organization to personalize it a bit.
++Just like in <<r_personal_avatar>>, you can upload an avatar for your organization to personalize it a bit.
+ Also just like personal accounts, you have a landing page for the organization that lists all of your repositories and can be viewed by other people.
+ 
+ Now let's cover some of the things that are a bit different with an organizational account.
+@@ -39,18 +38,16 @@
+ 
+ The Organization page shows you a simple dashboard of all the repositories, users and teams that are under this organization.
+ 
+-[[_org_page]]
+-.The Organization page
+-image::images/orgs-01-page.png[The Organization page]
++.The Organization page.
++image::images/orgs-01-page.png[]
+ 
+-To manage your Teams, you can click on the Teams sidebar on the right hand side of the page in <<_org_page>>.
++To manage your Teams, you can click on the Teams sidebar on the right hand side of the page in <<r_org_page>>.
+ This will bring you to a page you can use to add members to the team, add repositories to the team or manage the settings and access control levels for the team.
+ Each team can have read only, read/write or administrative access to the repositories.
+-You can change that level by clicking the ``Settings'' button in <<_team_page>>.
++You can change that level by clicking the ``Settings'' button in <<r_team_page>>.
+ 
+-[[_team_page]]
+-.The Team page
+-image::images/orgs-02-teams.png[The Team page]
++.The Team page.
++image::images/orgs-02-teams.png[]
+ 
+ When you invite someone to a team, they will get an email letting them know they've been invited.
+ 
+@@ -65,8 +62,7 @@
+ Organizations also give owners access to all the information about what went on under the organization.
+ You can go to the 'Audit Log' tab and see what events have happened at an organization level, who did them and where in the world they were done.
+ 
+-[[_the_audit_log]]
+-.The Audit log
+-image::images/orgs-03-audit.png[The Audit log]
++.The Audit log.
++image::images/orgs-03-audit.png[]
+ 
+ You can also filter down to specific types of events, specific places or specific people.
+diff -au ../../git/progit2/progit2/book/06-github/sections/5-scripting.asc /tmp/book/06-github/sections/5-scripting.asc.tmp
+--- ../../git/progit2/progit2/book/06-github/sections/5-scripting.asc	2020-07-04 16:36:46.733685573 +0900
++++ /tmp/book/06-github/sections/5-scripting.asc.tmp	2020-10-25 09:24:25.789972983 +0900
+@@ -5,7 +5,7 @@
+ Luckily for us, GitHub is really quite hackable in many ways.
+ In this section we'll cover how to use the GitHub hooks system and its API to make GitHub work how we want it to.
+ 
+-==== Services and Hooks
++==== Hooks
+ 
+ The Hooks and Services section of GitHub repository administration is the easiest way to have GitHub interact with external systems.
+ 
+@@ -13,19 +13,17 @@
+ 
+ First we'll take a look at Services.
+ Both the Hooks and Services integrations can be found in the Settings section of your repository, where we previously looked at adding Collaborators and changing the default branch of your project.
+-Under the ``Webhooks and Services'' tab you will see something like <<_services_hooks>>.
++Under the ``Webhooks and Services'' tab you will see something like <<r_services_hooks>>.
+ 
+-[[_services_hooks]]
+-.Services and Hooks configuration section
++.Services and Hooks configuration section.
+ image::images/scripting-01-services.png[Services and hooks]
+ 
+ There are dozens of services you can choose from, most of them integrations into other commercial and open source systems.
+ Most of them are for Continuous Integration services, bug and issue trackers, chat room systems and documentation systems.
+ We'll walk through setting up a very simple one, the Email hook.
+-If you choose ``email'' from the ``Add Service'' dropdown, you'll get a configuration screen like <<_service_config>>.
++If you choose ``email'' from the ``Add Service'' dropdown, you'll get a configuration screen like <<r_service_config>>.
+ 
+-[[_service_config]]
+-.Email service configuration
++.Email service configuration.
+ image::images/scripting-02-email-service.png[Email service]
+ 
+ In this case, if we hit the ``Add service'' button, the email address we specified will get an email every time someone pushes to the repository.
+@@ -42,11 +40,10 @@
+ 
+ Generally the way this works is you can setup a small web service to listen for a GitHub hook payload and then do something with the data when it is received.
+ 
+-To enable a hook, you click the ``Add webhook'' button in <<_services_hooks>>.
+-This will bring you to a page that looks like <<_web_hook>>.
++To enable a hook, you click the ``Add webhook'' button in <<r_services_hooks>>.
++This will bring you to a page that looks like <<r_web_hook>>.
+ 
+-[[_web_hook]]
+-.Web hook configuration
++.Web hook configuration.
+ image::images/scripting-03-webhook.png[Web hook]
+ 
+ The configuration for a web hook is pretty simple.
+@@ -59,7 +56,6 @@
+ Let's say we want to get an email if a specific person pushes to a specific branch of our project modifying a specific file.
+ We could fairly easily do that with code like this:
+ 
+-[source,ruby]
+ ----
+ require 'sinatra'
+ require 'json'
+@@ -101,19 +97,16 @@
+ For each hook you can dig down into when it was delivered, if it was successful and the body and headers for both the request and the response.
+ This makes it incredibly easy to test and debug your hooks.
+ 
+-[[_web_hook_debug]]
+-.Web hook debugging information
++.Web hook debugging information.
+ image::images/scripting-04-webhook-debug.png[Webhook debug]
+ 
+ The other great feature of this is that you can redeliver any of the payloads to test your service easily.
+ 
+-For more information on how to write webhooks and all the different event types you can listen for, go to the GitHub Developer documentation at https://developer.github.com/webhooks/[].
++For more information on how to write webhooks and all the different event types you can listen for, go to the GitHub Developer documentation at https://developer.github.com/webhooks/
+ 
+ ==== The GitHub API
+ 
+-(((GitHub, API)))
+-Services and hooks give you a way to receive push notifications about events that happen on your repositories, but what if you need more information about these events?
+-What if you need to automate something like adding collaborators or labeling issues?
++Services and hooks give you a way to receive push notifications about events that happen on your repositories, but what if you need more information about these events? What if you need to automate something like adding collaborators or labeling issues?
+ 
+ This is where the GitHub API comes in handy.
+ GitHub has tons of API endpoints for doing nearly anything you can do on the website in an automated fashion.
+@@ -125,47 +118,9 @@
+ This could be a user or read-only information on an open source project.
+ For example, if we want to know more about a user named ``schacon'', we can run something like this:
+ 
+-[source,javascript]
+-----
+-$ curl https://api.github.com/users/schacon
+-{
+-  "login": "schacon",
+-  "id": 70,
+-  "avatar_url": "https://avatars.githubusercontent.com/u/70",
+-# …
+-  "name": "Scott Chacon",
+-  "company": "GitHub",
+-  "following": 19,
+-  "created_at": "2008-01-27T17:19:28Z",
+-  "updated_at": "2014-06-10T02:37:23Z"
+-}
+-----
+-
+ There are tons of endpoints like this to get information about organizations, projects, issues, commits -- just about anything you can publicly see on GitHub.
+ You can even use the API to render arbitrary Markdown or find a `.gitignore` template.
+ 
+-[source,javascript]
+-----
+-$ curl https://api.github.com/gitignore/templates/Java
+-{
+-  "name": "Java",
+-  "source": "*.class
+-
+-# Mobile Tools for Java (J2ME)
+-.mtj.tmp/
+-
+-# Package Files #
+-*.jar
+-*.war
+-*.ear
+-
+-# virtual machine crash logs, see https://www.java.com/en/download/help/error_hotspot.xml
+-hs_err_pid*
+-"
+-}
+-----
+-
+-
+ ==== Commenting on an Issue
+ 
+ However, if you want to do an action on the website such as comment on an Issue or Pull Request or if you want to view or interact with private content, you'll need to authenticate.
+@@ -174,8 +129,7 @@
+ You can use basic authentication with just your username and password, but generally it's a better idea to use a personal access token.
+ You can generate this from the ``Applications'' tab of your settings page.
+ 
+-[[_access_token]]
+-.Generate your access token from the ``Applications'' tab of your settings page
++.Generate your access token from the ``Applications'' tab of your settings page.
+ image::images/scripting-05-access-token.png[Access Token]
+ 
+ It will ask you which scopes you want for this token and a description.
+@@ -193,32 +147,9 @@
+ Let's say we want to leave a comment on a specific issue, Issue #6.
+ To do so we have to do an HTTP POST request to `repos/<user>/<repo>/issues/<num>/comments` with the token we just generated as an Authorization header.
+ 
+-[source,javascript]
+-----
+-$ curl -H "Content-Type: application/json" \
+-       -H "Authorization: token TOKEN" \
+-       --data '{"body":"A new comment, :+1:"}' \
+-       https://api.github.com/repos/schacon/blink/issues/6/comments
+-{
+-  "id": 58322100,
+-  "html_url": "https://github.com/schacon/blink/issues/6#issuecomment-58322100",
+-  ...
+-  "user": {
+-    "login": "tonychacon",
+-    "id": 7874698,
+-    "avatar_url": "https://avatars.githubusercontent.com/u/7874698?v=2",
+-    "type": "User",
+-  },
+-  "created_at": "2014-10-08T07:48:19Z",
+-  "updated_at": "2014-10-08T07:48:19Z",
+-  "body": "A new comment, :+1:"
+-}
+-----
++Now if you go to that issue, you can see the comment that we just successfully posted as in <<r_api_comment>>.
+ 
+-Now if you go to that issue, you can see the comment that we just successfully posted as in <<_api_comment>>.
+-
+-[[_api_comment]]
+-.A comment posted from the GitHub API
++.A comment posted from the GitHub API.
+ image::images/scripting-06-comment.png[API Comment]
+ 
+ You can use the API to do just about anything you can do on the website -- creating and setting milestones, assigning people to Issues and Pull Requests, creating and changing labels, accessing commit data, creating new commits and branches, opening, closing or merging Pull Requests, creating and editing teams, commenting on lines of code in a Pull Request, searching the site and on and on.
+@@ -233,7 +164,6 @@
+ 
+ Let's say you set up a webhook on your repository that hits a small web service that checks for a `Signed-off-by` string in the commit message.
+ 
+-[source,ruby]
+ ----
+ require 'httparty'
+ require 'sinatra'
+@@ -282,21 +212,18 @@
+ In this case you can send a state ('success', 'failure', 'error'), a description of what happened, a target URL the user can go to for more information and a ``context'' in case there are multiple statuses for a single commit.
+ For example, a testing service may provide a status and a validation service like this may also provide a status -- the ``context'' field is how they're differentiated.
+ 
+-If someone opens a new Pull Request on GitHub and this hook is set up, you may see something like <<_commit_status>>.
++If someone opens a new Pull Request on GitHub and this hook is set up, you may see something like <<r_commit_status>>.
+ 
+-[[_commit_status]]
+-.Commit status via the API
++.Commit status via the API.
+ image::images/scripting-07-status.png[Commit status]
+ 
+ You can now see a little green check mark next to the commit that has a ``Signed-off-by'' string in the message and a red cross through the one where the author forgot to sign off.
+ You can also see that the Pull Request takes the status of the last commit on the branch and warns you if it is a failure.
+ This is really useful if you're using this API for test results so you don't accidentally merge something where the last commit is failing tests.
+ 
+-==== Octokit
+-
+ Though we've been doing nearly everything through `curl` and simple HTTP requests in these examples, several open-source libraries exist that make this API available in a more idiomatic way.
+ At the time of this writing, the supported languages include Go, Objective-C, Ruby, and .NET.
+-Check out https://github.com/octokit[] for more information on these, as they handle much of the HTTP for you.
++Check out http://github.com/octokit[] for more information on these, as they handle much of the HTTP for you.
+ 
+ Hopefully these tools can help you customize and modify GitHub to work better for your specific workflows.
+ For complete documentation on the entire API as well as guides for common tasks, check out https://developer.github.com[].
+diff -au ../../git/progit2/progit2/book/07-git-tools/sections/advanced-merging.asc /tmp/book/07-git-tools/sections/advanced-merging.asc.tmp
+--- ../../git/progit2/progit2/book/07-git-tools/sections/advanced-merging.asc	2020-07-04 16:36:46.733685573 +0900
++++ /tmp/book/07-git-tools/sections/advanced-merging.asc.tmp	2020-10-25 09:24:25.796973313 +0900
+@@ -1,4 +1,4 @@
+-[[_advanced_merging]]
++[[r_advanced_merging]]
+ === Advanced Merging
+ 
+ Merging in Git is typically fairly easy.
+@@ -14,117 +14,30 @@
+ 
+ ==== Merge Conflicts
+ 
+-While we covered some basics on resolving merge conflicts in <<ch03-git-branching#_basic_merge_conflicts>>, for more complex conflicts, Git provides a few tools to help you figure out what's going on and how to better deal with the conflict.
++While we covered some basics on resolving merge conflicts in <<ch03-git-branching#r_basic_merge_conflicts>>, for more complex conflicts, Git provides a few tools to help you figure out what's going on and how to better deal with the conflict.
+ 
+ First of all, if at all possible, try to make sure your working directory is clean before doing a merge that may have conflicts.
+ If you have work in progress, either commit it to a temporary branch or stash it.
+ This makes it so that you can undo *anything* you try here.
+-If you have unsaved changes in your working directory when you try a merge, some of these tips may help you preserve that work.
++If you have unsaved changes in your working directory when you try a merge, some of these tips may help you lose that work.
+ 
+ Let's walk through a very simple example.
+ We have a super simple Ruby file that prints 'hello world'.
+ 
+-[source,ruby]
+-----
+-#! /usr/bin/env ruby
+-
+-def hello
+-  puts 'hello world'
+-end
+-
+-hello()
+-----
+-
+ In our repository, we create a new branch named `whitespace` and proceed to change all the Unix line endings to DOS line endings, essentially changing every line of the file, but just with whitespace.
+ Then we change the line ``hello world'' to ``hello mundo''.
+ 
+-[source,console]
+-----
+-$ git checkout -b whitespace
+-Switched to a new branch 'whitespace'
+-
+-$ unix2dos hello.rb
+-unix2dos: converting file hello.rb to DOS format ...
+-$ git commit -am 'Convert hello.rb to DOS'
+-[whitespace 3270f76] Convert hello.rb to DOS
+- 1 file changed, 7 insertions(+), 7 deletions(-)
+-
+-$ vim hello.rb
+-$ git diff -b
+-diff --git a/hello.rb b/hello.rb
+-index ac51efd..e85207e 100755
+---- a/hello.rb
+-+++ b/hello.rb
+-@@ -1,7 +1,7 @@
+- #! /usr/bin/env ruby
+-
+- def hello
+--  puts 'hello world'
+-+  puts 'hello mundo'^M
+- end
+-
+- hello()
+-
+-$ git commit -am 'Use Spanish instead of English'
+-[whitespace 6d338d2] Use Spanish instead of English
+- 1 file changed, 1 insertion(+), 1 deletion(-)
+-----
+-
+ Now we switch back to our `master` branch and add some documentation for the function.
+ 
+-[source,console]
+-----
+-$ git checkout master
+-Switched to branch 'master'
+-
+-$ vim hello.rb
+-$ git diff
+-diff --git a/hello.rb b/hello.rb
+-index ac51efd..36c06c8 100755
+---- a/hello.rb
+-+++ b/hello.rb
+-@@ -1,5 +1,6 @@
+- #! /usr/bin/env ruby
+-
+-+# prints out a greeting
+- def hello
+-   puts 'hello world'
+- end
+-
+-$ git commit -am 'Add comment documenting the function'
+-[master bec6336] Add comment documenting the function
+- 1 file changed, 1 insertion(+)
+-----
+-
+ Now we try to merge in our `whitespace` branch and we'll get conflicts because of the whitespace changes.
+ 
+-[source,console]
+-----
+-$ git merge whitespace
+-Auto-merging hello.rb
+-CONFLICT (content): Merge conflict in hello.rb
+-Automatic merge failed; fix conflicts and then commit the result.
+-----
+-
+-[[_abort_merge]]
++[[r_abort_merge]]
+ ===== Aborting a Merge
+ 
+ We now have a few options.
+ First, let's cover how to get out of this situation.
+ If you perhaps weren't expecting conflicts and don't want to quite deal with the situation yet, you can simply back out of the merge with `git merge --abort`.
+ 
+-[source,console]
+-----
+-$ git status -sb
+-## master
+-UU hello.rb
+-
+-$ git merge --abort
+-
+-$ git status -sb
+-## master
+-----
+-
+ The `git merge --abort` option tries to revert back to your state before you ran the merge.
+ The only cases where it may not be able to do this perfectly would be if you had unstashed, uncommitted changes in your working directory when you ran it, otherwise it should work fine.
+ 
+@@ -141,20 +54,10 @@
+ If you see that you have a lot of whitespace issues in a merge, you can simply abort it and do it again, this time with `-Xignore-all-space` or `-Xignore-space-change`.
+ The first option ignores whitespace *completely* when comparing lines, the second treats sequences of one or more whitespace characters as equivalent.
+ 
+-[source,console]
+-----
+-$ git merge -Xignore-space-change whitespace
+-Auto-merging hello.rb
+-Merge made by the 'recursive' strategy.
+- hello.rb | 2 +-
+- 1 file changed, 1 insertion(+), 1 deletion(-)
+-----
+-
+ Since in this case, the actual file changes were not conflicting, once we ignore the whitespace changes, everything merges just fine.
+ 
+ This is a lifesaver if you have someone on your team who likes to occasionally reformat everything from spaces to tabs or vice-versa.
+ 
+-[[_manual_remerge]]
+ ===== Manual File Re-merging
+ 
+ Though Git handles whitespace pre-processing pretty well, there are other types of changes that perhaps Git can't handle automatically, but are scriptable fixes.
+@@ -173,52 +76,12 @@
+ 
+ You can extract a copy of each of these versions of the conflicted file with the `git show` command and a special syntax.
+ 
+-[source,console]
+-----
+-$ git show :1:hello.rb > hello.common.rb
+-$ git show :2:hello.rb > hello.ours.rb
+-$ git show :3:hello.rb > hello.theirs.rb
+-----
+-
+ If you want to get a little more hard core, you can also use the `ls-files -u` plumbing command to get the actual SHA-1s of the Git blobs for each of these files.
+ 
+-[source,console]
+-----
+-$ git ls-files -u
+-100755 ac51efdc3df4f4fd328d1a02ad05331d8e2c9111 1	hello.rb
+-100755 36c06c8752c78d2aff89571132f3bf7841a7b5c3 2	hello.rb
+-100755 e85207e04dfdd5eb0a1e9febbc67fd837c44a1cd 3	hello.rb
+-----
+-
+ The `:1:hello.rb` is just a shorthand for looking up that blob SHA-1.
+ 
+ Now that we have the content of all three stages in our working directory, we can manually fix up theirs to fix the whitespace issue and re-merge the file with the little-known `git merge-file` command which does just that.
+ 
+-[source,console]
+-----
+-$ dos2unix hello.theirs.rb
+-dos2unix: converting file hello.theirs.rb to Unix format ...
+-
+-$ git merge-file -p \
+-    hello.ours.rb hello.common.rb hello.theirs.rb > hello.rb
+-
+-$ git diff -b
+-diff --cc hello.rb
+-index 36c06c8,e85207e..0000000
+---- a/hello.rb
+-+++ b/hello.rb
+-@@@ -1,8 -1,7 +1,8 @@@
+-  #! /usr/bin/env ruby
+-
+- +# prints out a greeting
+-  def hello
+--   puts 'hello world'
+-+   puts 'hello mundo'
+-  end
+-
+-  hello()
+-----
+-
+ At this point we have nicely merged the file.
+ In fact, this actually works better than the `ignore-space-change` option because this actually fixes the whitespace changes before merge instead of simply ignoring them.
+ In the `ignore-space-change` merge, we actually ended up with a few lines with DOS line endings, making things mixed.
+@@ -226,82 +89,17 @@
+ If you want to get an idea before finalizing this commit about what was actually changed between one side or the other, you can ask `git diff` to compare what is in your working directory that you're about to commit as the result of the merge to any of these stages.
+ Let's go through them all.
+ 
+-To compare your result to what you had in your branch before the merge, in other words, to see what the merge introduced, you can run `git diff --ours`:
+-
+-[source,console]
+-----
+-$ git diff --ours
+-* Unmerged path hello.rb
+-diff --git a/hello.rb b/hello.rb
+-index 36c06c8..44d0a25 100755
+---- a/hello.rb
+-+++ b/hello.rb
+-@@ -2,7 +2,7 @@
+-
+- # prints out a greeting
+- def hello
+--  puts 'hello world'
+-+  puts 'hello mundo'
+- end
+-
+- hello()
+-----
++To compare your result to what you had in your branch before the merge, in other words, to see what the merge introduced, you can run `git diff --ours`
+ 
+ So here we can easily see that what happened in our branch, what we're actually introducing to this file with this merge, is changing that single line.
+ 
+ If we want to see how the result of the merge differed from what was on their side, you can run `git diff --theirs`.
+ In this and the following example, we have to use `-b` to strip out the whitespace because we're comparing it to what is in Git, not our cleaned up `hello.theirs.rb` file.
+ 
+-[source,console]
+-----
+-$ git diff --theirs -b
+-* Unmerged path hello.rb
+-diff --git a/hello.rb b/hello.rb
+-index e85207e..44d0a25 100755
+---- a/hello.rb
+-+++ b/hello.rb
+-@@ -1,5 +1,6 @@
+- #! /usr/bin/env ruby
+-
+-+# prints out a greeting
+- def hello
+-   puts 'hello mundo'
+- end
+-----
+-
+ Finally, you can see how the file has changed from both sides with `git diff --base`.
+ 
+-[source,console]
+-----
+-$ git diff --base -b
+-* Unmerged path hello.rb
+-diff --git a/hello.rb b/hello.rb
+-index ac51efd..44d0a25 100755
+---- a/hello.rb
+-+++ b/hello.rb
+-@@ -1,7 +1,8 @@
+- #! /usr/bin/env ruby
+-
+-+# prints out a greeting
+- def hello
+--  puts 'hello world'
+-+  puts 'hello mundo'
+- end
+-
+- hello()
+-----
+-
+ At this point we can use the `git clean` command to clear out the extra files we created to do the manual merge bu