-
Notifications
You must be signed in to change notification settings - Fork 58
Should globbing be included as a server-side feature? #64
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
1.0 should either include or exclude features; not have any at risk. As for globbing, I strongly feel we should exclude it for reasons mentioned in the above threads, which also link to a 10-line client-side alternative I wrote. |
My vote is: +1 to what @RubenVerborgh said. |
Agree on exclusion. IMO - this has lingered for a long time when there are legitimate alternatives and it’s a good time to move from at risk to excluded in the next major version. |
Then I hereby conclude to not include globbing, unless any objections come up. (Since there is no text to be reviewed for not adding a feature, there is nothing more we can do process-wise.) |
Moved to "Done". IIRC; it is possible to automated that in the project board. |
Currently, the much-contentious Globbing mechanism is marked 'at risk' on the existing spec.
As part of the 1.0 spec we should decide its fate (either continue marking it at at-risk, or, preferably, decide one way or another).
Related issues:
The text was updated successfully, but these errors were encountered: