Merge pull request #163 from progit/remove-notes

Remove dead notes content

Author: ben

book/07-git-tools/sections/notes.asc

@@ -218,7 +218,7 @@ In <<_private_team>> and <<_commit_ranges>> we cover the `branchA..branchB` synt
 
 In <<_merge_log>> and <<_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 <<_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 <<_git_notes>> we use the `--notes=` option to display notes inline in the log output, and in <<_git_reflog>> we use the `-g` option to view the Git reflog through this tool instead of doing branch traversal.
+In <<_git_reflog>> we use the `-g` option to view the Git reflog through this tool instead of doing branch traversal.
 
 In <<_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.
 
@@ -253,7 +253,7 @@ We also use it in several of the examples in <<_contributing_project>>.
 
 We use it to fetch a single specific reference that is outside of the default space in <<_pr_refs>> and we see how to fetch from a bundle in <<_bundling>>.
 
-We set up highly custom refspecs in order to make `git fetch` do something a little different than the default in <<_getting_notes>> and <<_refspec>>.
+We set up highly custom refspecs in order to make `git fetch` do something a little different than the default in <<_refspec>>.
 
 ==== git pull
 
@@ -277,8 +277,6 @@ Throughout <<_contributing_project>> we see several examples of using `git push`
 
 We see how to use it to share tags that you have made with the `--tags` option in <<_sharing_tags>>.
 
-In <<_sharing_notes>> we use it in a slightly less common way to share references for commit notes -- references that sit outside of the normal refs namespace.
-
 In <<_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 <<_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.

book/C-git-commands/1-git-commands.asc

@@ -65,7 +65,6 @@
       "sections/credentials.asc": 0,
       "sections/debugging.asc": 0,
       "sections/interactive-staging.asc": 0,
-      "sections/notes.asc": 0,
       "sections/replace.asc": 0,
       "sections/rerere.asc": 0,
       "sections/reset.asc": 0,