date: Rework argument processing #6560
Closed
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
|
GNU testsuite comparison: |
|
Doesn't this duplicate some of the work in #6142 ? |
7906ff7 to
9477ba0
Compare
|
GNU testsuite comparison: |
9477ba0 to
cc101fa
Compare
|
@RenjiSann it is still marked as draft, are you still working on it? thanks |
|
I am not working on this anymore. I don't really remember the context of it either. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
This pull request addresses several points on the argument processing of
date:--date,--file,--reference, and--resolution(not yet implemented).--date,--fileand--referencearguments override their previous introduction.This is still work in progress, as I also would like to fix the distinction between FORMAT positional arguments (starting with +) and date positional arguments.