This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PING^5 [PATCH, GCC 5] PR 70613, -fabi-version docs don't match implementation
- From: Mike Stump <mikestump at comcast dot net>
- To: Sandra Loosemore <sandra at codesourcery dot com>
- Cc: Ramana Radhakrishnan <ramana dot gcc at googlemail dot com>, Jim Wilson <jim dot wilson at linaro dot org>, "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>
- Date: Tue, 17 May 2016 10:49:42 -0700
- Subject: Re: PING^5 [PATCH, GCC 5] PR 70613, -fabi-version docs don't match implementation
- Authentication-results: sourceware.org; auth=none
- References: <CABXYE2WuUm5xu5F6oJKkFjXPJJ+VagHR0JJCaX8RmCo=G3pu3g at mail dot gmail dot com> <573A642B dot 4010906 at codesourcery dot com> <CAJA7tRYA_7XmBL+4GFqA6mCqDrrf8q_Nc-y9YfUN0RCP9rP=uQ at mail dot gmail dot com> <573B3671 dot 3060908 at codesourcery dot com>
On May 17, 2016, at 8:19 AM, Sandra Loosemore <sandra@codesourcery.com> wrote:
>
> I thought I remembered mail going by that changes to a release branch require RM approval too.
For time to time, the RM can close any release branch at any time for any reason. :-) For example, a gcc 3.2.x release branch has been closed for any checkins. When they are trying to get a release out, they may say, no checkins til the release is made and so on. In general, they update https://gcc.gnu.org/ to list the state of each branch. The non-permanent closures are generally only til the next release. The permanent closures are because we are removing support for an old release because we have a new release now.