@nnussbaum thanks for this contribution! You did it well ... except for one minor thing.

In the table that you fill in for each pull request, in the Branch cell you left the original message: "master for features and deprecations / lowest applicable and maintained version otherwise"

This is in fact a message for you (the person who submitted the pull request). You need to think the best branch on which the pull request should be merged. These are the rules:

• If it's a new feature, select "master"
• If it's a bug, select the oldest (but maintained) Symfony branch which suffers that error.

In this case it's a bug and the oldest maintained branch who suffers the issue is 2.3, so you need to put 2.3 as the value of the Branch row in the table. Thanks!

Arf, just saw that... Wont make the mistake again! Thank you :)

A note to you from Symfony maintainers:

Thank you for making this contribution to Symfony. As you know, we prepared some simple issues so you could submit real pull requests fixing real issues. However, as there are more people than issues, we'll need to close some repeated pull requests without merging them.

We are not sure about the criteria we'll use to close repeated pull requests (first one wins? randomly selected one wins?). So maybe your pull request is closed without merging it. But please, don't feel bad about that. You did great and you actually contributed to Symfony 🎉 If this pull request doesn't get merged, there will be more opportunities to send new pull requests.

Thank you for being part of the (big and awesome) Symfony Community!