-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
[3.6] bpo-31106: Fix handling of erros in posix_fallocate() and posix_fadvise() (GH-3000) (GH-3000) #4101
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
Conversation
…se() (pythonGH-3000) (pythonGH-3000) (cherry picked from commit d4b93e2)
@socketpair and @larryhastings: Backport status check is done, and it's a failure ❌ . |
1 similar comment
@socketpair and @larryhastings: Backport status check is done, and it's a failure ❌ . |
Well, what should I do ? I have no access to this branch. |
@socketpair and @larryhastings: Backport status check is done, and it's a success ✅ . |
I just saw the comment in the bpo, seems like a news entry is needed. |
@socketpair and @larryhastings: Backport status check is done, and it's a failure ❌ . |
What can I do in order to merge this branch to Python 3.6 ? |
@socketpair Please create your own backport PR and add the news entry there.. |
Original PR was merged without NEWS, let's add the record in separate PR |
@socketpair and @larryhastings: Backport status check is done, and it's a success ✅ . |
@asvetlov: Please replace |
Thanks, @asvetlov! |
(cherry picked from commit d4b93e2)
https://bugs.python.org/issue31106