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

[VarExporter] fix handling of __sleep() #29209

Merged
merged 1 commit into from Nov 14, 2018

Conversation

Projects
None yet
2 participants
@nicolas-grekas
Member

nicolas-grekas commented Nov 13, 2018

Q A
Branch? 4.2
Bug fix? yes
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets #29118
License MIT
Doc PR -

@nicolas-grekas nicolas-grekas added this to the 4.2 milestone Nov 13, 2018

@nicolas-grekas nicolas-grekas force-pushed the nicolas-grekas:ve-fix branch from c60b902 to 6ff3b1e Nov 14, 2018

@nicolas-grekas nicolas-grekas force-pushed the nicolas-grekas:ve-fix branch from 6ff3b1e to 46e2ecd Nov 14, 2018

@nicolas-grekas nicolas-grekas merged commit 46e2ecd into symfony:master Nov 14, 2018

1 of 3 checks passed

continuous-integration/appveyor/pr Waiting for AppVeyor build to complete
Details
continuous-integration/travis-ci/pr The Travis CI build is in progress
Details
fabbot.io Your code looks good.
Details

nicolas-grekas added a commit that referenced this pull request Nov 14, 2018

bug #29209 [VarExporter] fix handling of __sleep() (nicolas-grekas)
This PR was merged into the 4.2-dev branch.

Discussion
----------

[VarExporter] fix handling of __sleep()

| Q             | A
| ------------- | ---
| Branch?       | 4.2
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | #29118
| License       | MIT
| Doc PR        | -

Commits
-------

46e2ecd [VarExporter] fix handling of __sleep()

@nicolas-grekas nicolas-grekas deleted the nicolas-grekas:ve-fix branch Nov 14, 2018

@fabpot fabpot referenced this pull request Nov 16, 2018

Merged

Release v4.2.0-BETA2 #29237

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment