Skip to content

[3.6] bpo-31106: Fix handling of erros in posix_fallocate() and posix… #3088

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

Closed
wants to merge 1 commit into from

Conversation

larryhastings
Copy link
Contributor

@larryhastings larryhastings commented Aug 14, 2017

…_fadvise() (GH-3000) (GH-3000)

(cherry picked from commit d4b93e2)

https://bugs.python.org/issue31106

Copy link
Member

@serhiy-storchaka serhiy-storchaka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems the code is not different in 3.6 and master. Such kind of backports doesn't need a special review.

@serhiy-storchaka
Copy link
Member

I just wondering why the commit message contains doubled "(GH-3000)".

And both changes need NEWS entries. But it may be easier to add them by separate commits.

@benjaminp benjaminp closed this Sep 28, 2017
@benjaminp benjaminp deleted the backport-d4b93e2-3.6 branch September 28, 2017 03:28
@benjaminp
Copy link
Contributor

I deleted the backport branch because it seemed old. Feel free to restore if this still needs to happen.

@socketpair
Copy link
Contributor

socketpair commented Dec 23, 2017

What can I do in order to merge this branch to Python 3.6 ?

Does it differ from #4101 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants