summaryrefslogtreecommitdiff
path: root/benchmark
diff options
context:
space:
mode:
authorDaniel Colson <danieljamescolson@gmail.com>2023-01-26 20:39:27 -0500
committergit <svn-admin@ruby-lang.org>2023-01-27 21:06:39 +0000
commit8429134d0d942f89fa022af38e065eb33c83523a (patch)
treea36091121560c59032054ebbfc0089485fc59d3b /benchmark
parent7d4395cb690c4b6be41bc51b25a8a5cda6210a81 (diff)
[rubygems/rubygems] Don't warn on bundler binstubs --standalone --allHEADmaster
Prior to this commit `bundle binstubs --standalone --all` would output a warning about not being able to generate a standalone binstub for bundler. This warning predates the `--all` option, and I don't think it makes sense in this context. The warning makes good sense when explicitly trying to generate a bundler standalone binstub with `bundle binstubs bundler --standalone`, since that command won't do what the user might have expected. But `--all` is not specifically asking for bundler, and having it report each time that the bundler binstubs could not be generated does not seem particularly helpful. The only way to make that warning go away would be to stop using `--standalone --all`. This commit skips the warning when running with the `--all` option. https://github.com/rubygems/rubygems/commit/e6a72e19eb
Diffstat (limited to 'benchmark')
0 files changed, 0 insertions, 0 deletions