Sync with 1.8.1.1

diff --combined Documentation/git.txt
index c03b7adc97a98b41f6f4c709fa5e0a1ee4e71cd5,276491223a1e4536cd7a6913b1bf1fb75f7012b0..555250dfa0272f890b6d427ff61b4ea42ba0b814
--- 1/Documentation/git.txt
--- 2/Documentation/git.txt
+++ b/Documentation/git.txt
@@@ -43,9 -43,10 +43,10 @@@ unreleased) version of git, that is ava
  branch of the `git.git` repository.
  Documentation for older releases are available here:
  
- * link:v1.8.1/git.html[documentation for release 1.8.1]
+ * link:v1.8.1.1/git.html[documentation for release 1.8.1.1]
  
  * release notes for
+   link:RelNotes/1.8.1.1.txt[1.8.1.1],
    link:RelNotes/1.8.1.txt[1.8.1].
  
  * link:v1.8.0.3/git.html[documentation for release 1.8.0.3]
@@@ -428,11 -429,6 +429,11 @@@ help ...`
        Do not use replacement refs to replace git objects. See
        linkgit:git-replace[1] for more information.
  
 +--literal-pathspecs::
 +      Treat pathspecs literally, rather than as glob patterns. This is
 +      equivalent to setting the `GIT_LITERAL_PATHSPECS` environment
 +      variable to `1`.
 +
  
  GIT COMMANDS
  ------------
@@@ -809,16 -805,6 +810,16 @@@ for further details
        as a file path and will try to write the trace messages
        into it.
  
 +GIT_LITERAL_PATHSPECS::
 +      Setting this variable to `1` will cause git to treat all
 +      pathspecs literally, rather than as glob patterns. For example,
 +      running `GIT_LITERAL_PATHSPECS=1 git log -- '*.c'` will search
 +      for commits that touch the path `*.c`, not any paths that the
 +      glob `*.c` matches. You might want this if you are feeding
 +      literal paths to git (e.g., paths previously given to you by
 +      `git ls-tree`, `--raw` diff output, etc).
 +
 +
  Discussion[[Discussion]]
  ------------------------