Tools: legacy-param options for param_parse.py #31628
Merged
+35
−2
Conversation
This file contains hidden or 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
robertlong13
force-pushed
the
pr/param-parse-no-legacy-option
branch
from
30c22bf to
576b1ec
Compare
robertlong13
force-pushed
the
pr/param-parse-no-legacy-option
branch
from
576b1ec to
4e67d4a
Compare
peterbarker
approved these changes
Dec 1, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
On its own, this is a non-functional change.
build_parameters.shgenerates identical output before and after (the only diff being the gzip files, but those are because we don't pass-nwhen we call gzip)This adds the option for a caller to explicitly decide if they want the legacy parameters included in the output.