`--quiet` doesn't seem to be working as expected.

bash completions: use proper Bash syntax

Bump ethon from 0.11.0 to 0.12.0 in /docs

Bumps [ethon](https://github.com/typhoeus/ethon) from 0.11.0 to 0.12.0.
- [Release notes](https://github.com/typhoeus/ethon/releases)
- [Changelog](https://github.com/typhoeus/ethon/blob/v0.12.0/CHANGELOG.md)
- [Commits](https://github.com/typhoeus/ethon/compare/v0.11.0...v0.12.0

)

Signed-off-by: dependabot[bot] <support@dependabot.com>

compat: correct MacOS.prefer_64_bit? deprecation

spec_helper: tweak parallel tests handling.

- only hide filtered runs in parallel (where they are super noisy)
- only send SimpleCov coverage once to Coveralls

config: better handle missing variables.

We don’t really have a better solution than this because of how the auto-updater’s Bash code worked on the version they are updating from. Users will never hit this more than once.

Fixes #5513

Update Shell-Completion.md

Please see https://discourse.brew.sh/t/bash-completion-and-brew-instructions-for-setting-up-completions/3808 for details...

cleanup: make cache directory for clean file.

This means the `.cleaned` file is correctly created for periodic
cleanup handling.

utils: don't look for bundler executable.

This exists sometimes and not others it seems.

extend/ARGV: don't warn on --bottle-arch=.

hardware: no special penryn CFLAGS.

Update deprecations

Fixes #5504.

These are the same as `core2` (at least for `gcc`).

Fixes #5502.

- Add some `odeprecated`
- Make some `odeprecated` now `odisabled`
- Remove `odisabled` code.
- Remove old update migrations
- Remove GCC 4.0 compiler
- Remove Tiger-only code
- Remove 32-bit-only code
- Remove use of LD64
- Remove GCC 4.3 - 4.8 support.

Use -march=native for non-bottle source builds [Linux]

Fix deprecated Rubygems options

Use `bundle install` in more places.

In February 2013, Rubygems 2.0.0 deprecated [1] the `--[no-]ri` and `--[no-]rdoc` options, replacing them with the new `--[no-]document` option.

Almost five years later, Rubygems finally dropped support [2] for the long-deprecated `--[no-]ri` and `--[no-]rdoc` options.

This removal causes `bundle install` to **fail for fresh Homebrew checkouts** if Rubygems 3.0.x or newer is installed, which will happen if the user runs `gem update --system` on Ruby 2.3.0 or later. [3]

This also affects the system Ruby built into macOS 10.13 and 10.14.

Steps to reproduce:

```
$ sudo /usr/bin/gem update -N --system
[…]
Installing RubyGems 3.0.2
ERROR:  While executing gem ... (Errno::EPERM)
    Operation not permitted @ rb_sysopen - /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/bin/gem
$ gem --version 2>/dev/null
3.0.2
$ cd "$(mktemp -d)"
$ git clone --depth=1 https://github.com/Homebrew/brew.git
[…]
$ cd brew
$ export HOMEBREW_PATH=bin  # in case shellcheck is not installed
$ bin/brew style Library/Homebrew/extend/ENV/std.rb
==> Installing or updating 'rubocop' gem
Error: invalid option: --no-ri
```

(Note: The above steps will not touch an existing Homebrew installation, and won’t even require Homebrew to be installed.)

This commit replaces the deprecated options with the new `--no-document` option, which has been around since Rubygems 2.0.0. It is therefore safe for use on all supported platforms.

[1]: https://blog.rubygems.org/2013/02/24/2.0.0-released.html
[2]: https://github.com/rubygems/rubygems/pull/2354
[3]: https://rubygems.org/gems/rubygems-update/versions

This provides a more consistent version for `rubocop` than relying on
`Homebrew.install_gem_setup_path!` (and we really want `brew style` to
provide consistent output).

This reverts commit c04d9cf6.

This reverts commit f8a6a346.

Disable cop for #set_cpu_flags, #set_cpu_cflags

In `extend/ENV/std.rb`, the methods `set_cpu_flags` and
`set_cpu_cflags` have been violating the `Naming/AccessorMethodName`
cop.

A recent modification in #7e13b374 woke up the cop. That means we’re
likely dealing with legacy code here, predating the introduction of
RuboCop into Homebrew.

This commit disables the cop for either method. I believe refactoring
wouldn’t currently be worth the effort, especially given that
`#set_cpu_cflags` is mostly called without arguments.

Add docs/Linuxbrew.md

Merge pull request #5494 from Homebrew/dependabot/bundler/Library/Homebrew/vendor/jaro_winkler-1.5.2

Bump jaro_winkler from 1.5.1 to 1.5.2 in /Library/Homebrew/vendor

Bump i18n from 1.4.0 to 1.5.1 in /Library/Homebrew/vendor

ENV: default CFLAGS to bottle values.

Bump html-pipeline from 2.9.2 to 2.10.0 in /docs