Merge branch 'ma/mailing-list-address-in-git-help'

Doc update.

* ma/mailing-list-address-in-git-help:
git doc: direct bug reporters to mailing list archive

diff --combined Documentation/git.txt
index 08e533d62b7f20a026b21d0dc8e9f35f4111b49e,b556f989f194e0bc9ca2fe104721b81fdec85870..2ac9b1c7fe00fea0772d5269121ffdf424435b96
--- 1/Documentation/git.txt
--- 2/Documentation/git.txt
+++ b/Documentation/git.txt
@@@ -76,7 -76,7 +76,7 @@@ Note that omitting the `=` in `git -c f
  `foo.bar` to the boolean true value (just like `[foo]bar` would in a
  config file). Including the equals but with an empty value (like `git -c
  foo.bar= ...`) sets `foo.bar` to the empty string which `git config
 ---bool` will convert to `false`.
 +--type=bool` will convert to `false`.
  
  --exec-path[=<path>]::
        Path to wherever your core Git programs are installed.
@@@ -599,8 -599,8 +599,8 @@@ trace messages into this file descripto
  +
  Alternatively, if the variable is set to an absolute path
  (starting with a '/' character), Git will interpret this
 -as a file path and will try to write the trace messages
 -into it.
 +as a file path and will try to append the trace messages
 +to it.
  +
  Unsetting the variable, or setting it to empty, "0" or
  "false" (case insensitive) disables trace messages.
@@@ -858,7 -858,9 +858,9 @@@ Reporting Bug
  
  Report bugs to the Git mailing list <git@vger.kernel.org> where the
  development and maintenance is primarily done.  You do not have to be
- subscribed to the list to send a message there.
+ subscribed to the list to send a message there.  See the list archive
+ at https://public-inbox.org/git for previous bug reports and other
+ discussions.
  
  Issues which are security relevant should be disclosed privately to
  the Git Security mailing list <git-security@googlegroups.com>.