On Thu, 4 Apr 2013, Jack Howarth wrote: > On Wed, Apr 03, 2013 at 03:23:36PM +0200, Richard Biener wrote: > > > > Status > > ====== > > > > The GCC 4.7 branch is ready for a release candidate of GCC 4.7.3 > > which I will do tomorrow if no serious issue shows up until then. > > The branch is frozen now, all changes require release manager approval > > until the final release of GCC 4.7.3 which should happen roughly > > one week after the release candidate. > > > > > > Quality Data > > ============ > > > > Priority # Change from Last Report > > -------- --- ----------------------- > > P1 0 > > P2 86 + 2 > > P3 6 - 12 > > -------- --- ----------------------- > > Total 92 - 10 > > > > > > Previous Report > > =============== > > > > http://gcc.gnu.org/ml/gcc/2012-09/msg00182.html > > > > > > The next report will be sent by me after the release > > FYI, http://gcc.gnu.org/ml/gcc-patches/2012-06/msg01181.html to backport the > fix for PR debug/53453 > has been approved since last July but never applied to gcc-4_7-branch... > > http://gcc.gnu.org/ml/gcc-patches/2012-06/msg01265.html > > If we can't get this into 4.7.3 and it at least go into gcc-4_7-branch when > it reopens in > hopes of eventually landing in 4.7.4?
Sure, it will be fine for 4.7.4. _Please_ get yourself SVN write access or at least point out to reviewers that you are not able to commit yourself (in which case I will get curious if you even have a copyright assignment in place - mere mortals can only check MAINTAINERS). Richard.
