Reinstate nonfunctional --no-daemonize, --daemonize options that warn #381
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
simi
approved these changes
Oct 12, 2023
olleolleolle
force-pushed
the
reinstate-a-nonfunctional-no-daemonize-option
branch
from
2bfca05
to
173a27a
Compare
olleolleolle
changed the title
|
See ruby/psych#655 for the reason why JRuby fails its build. |
|
As a follow-up, I have now released gemstash-2.7.1-java.gem, too. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Reinstate a
--daemonizeand--no-daemonizewhich only warn.Follow-up to #378 and fixes the problem in #380.
Tasks:
I will abide by the code of conduct.