[Session] Fixed Backward Compatibility issue with getFlashes()
[WebProfiler] added phpinfo
added link in config panel
merged branch Tobion/phpinfo (PR #4119)

Commits
-------

b180c01 added link in config panel
3551b29 [WebProfiler] added phpinfo

Discussion
----------

[WebProfiler] added phpinfo page

This adds a page with the `phpinfo`. It is accessible from the toolbar as link from the php logo that did not link to anywhere before.
I thought about including it as part of the profiler layout (with the panels etc.). But since it does not belong to a specific request, I think it's more clear to have a dedicated page that most people are familiar with.
Including it in the layout would also require modifying the HTML code returned by the phpinfo function.

---------------------------------------------------------------------------

by lsmith77 at 2012-04-26T06:39:43Z

+1

---------------------------------------------------------------------------

by Baachi at 2012-04-26T06:48:21Z

:+1:
merged branch willdurand/fix-session-bc (PR #4114)

Commits
-------

6756f28 [Session] Fixed Backward Compatibility issue with getFlashes()

Discussion
----------

[Session] Fixed Backward Compatibility issue with getFlashes()

---------------------------------------------------------------------------

by fabpot at 2012-04-25T22:35:42Z

ping @drak

---------------------------------------------------------------------------

by willdurand at 2012-04-25T22:37:01Z

By the way, I had this issue on a real application I upgraded from Symfony2 2.0.x to 2.1 (and written by @Seldaek)

The code looks like:

``` php
<?php
// in a controller

$this->session->setFlash('foo', array(
    'code' => 'success',
    'message' => 'lalala',
    'params' => array())
);
```

---------------------------------------------------------------------------

by Seldaek at 2012-04-26T07:25:03Z

Yup, to be fair in retrospective maybe that should have been translated in the controller directly (that's why it had message + params as an array), but this is code that predates 2.0 by at least six months, so it was obviously not clear what best practices were. Anyway it seems it can be fixed without much harm, so for the sake of safety and because I may not be the only crazy person having done this, it'd be good to fix IMO.
Updated danish translation.
Fixed the danish to be the same in all the validations..

English:
The value is not a country.

Danish translation in the latest commit:
Denne værdi er ikke et land.

Danish translation in the first commit and mine version:
Værdien er ikke et land

So this commit is simply to make the danish translation the same, and
not two different expressions..
merged branch hollodk/master (PR #4123)

Commits
-------

a1267a6 Fixed the danish to be the same in all the validations..
4092dc3 Updated danish translation.

Discussion
----------

Added some more danish translation

I have made this in two commits..

the first commit is new translations..

the second commit is where i have changed some translation to use the same danish grammer..
[Yaml] added CHANGELOG
[Translation] added CHANGELOG
[Templating] added CHANGELOG
[Serializer] added CHANGELOG
[Process] added CHANGELOG
[Locale] added CHANGELOG
Fixed a typo
[HttpKernel] added CHANGELOG
[HttpFoundation] added CHANGELOG
[Finder] added CHANGELOG
[Filesystem] added CHANGELOG
[EventDispatcher] added CHANGELOG