On Wed, 8 Apr 2015, Jonathan Wakely wrote:
>> The only drawback of this, and some similar cases, is that we now
>> risk referring to older versions on a release branch.
> Yes, I realised that problem when making the change and linking to the
> versions that were current at the time. One option woul
On 08/04/15 13:06 +0200, Gerald Pfeifer wrote:
On Sat, 6 Dec 2014, Jonathan Wakely wrote:
I'm also noting one old change in the GCC 4.5 page, and
removing/changing some links to the C++0x status table. The list of
features supported on trunk is fairly irrelevant to someone looking at
the 4.4 rel
On Sat, 6 Dec 2014, Jonathan Wakely wrote:
> I'm also noting one old change in the GCC 4.5 page, and
> removing/changing some links to the C++0x status table. The list of
> features supported on trunk is fairly irrelevant to someone looking at
> the 4.4 release notes, so I've linked to the docs for
On Sat, 6 Dec 2014, Jonathan Wakely wrote:
This adds recent libstdc++ updates to gcc-5/changes.html
Nice! Just a most minor change to end a list with a full stop
instead of a semi-colon. Applied.
Gerald
Index: changes.html
==
This adds recent libstdc++ updates to gcc-5/changes.html
I'm also noting one old change in the GCC 4.5 page, and
removing/changing some links to the C++0x status table. The list of
features supported on trunk is fairly irrelevant to someone looking at
the 4.4 release notes, so I've linked to the
