-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maintainer wanted #23
Labels
Comments
I'd be willing to co-maintain. We depend on this transitively through |
I'm happy to help out too, for the same reason. Not sure I can do active development, but I should've time for reviews and so on :) |
Merged
bors bot
added a commit
that referenced
this issue
Jun 7, 2021
27: Update to nom 6.x r=emilio a=tweksteen This is an upgrade to nom 6.x. It was tested via `cargo test`. @jethrogb Could you please review? Could you please also consider adding @emilio as maintainer (see #23)? Thanks. Old obsolete message: > This is an attempt at upgrading to nom 6.x. There is still an issue in `typed_token` about the expected lifetime of the input. @jonhoo, since you did the port to nom 5.x, you may have some insight on how to fix this. @jethrogb, any feedback is appreciated. Thanks. Bug: #26 Co-authored-by: Thiébaud Weksteen <tweek@google.com>
@jethrogb Do you still need comaintainers? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm currently reviewing PRs on a best-effort basis, which may take a month or so. If someone is willing to co-maintain this, that'd be great.
The text was updated successfully, but these errors were encountered: