From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15056 invoked by alias); 20 Aug 2012 12:31:20 -0000 Received: (qmail 15044 invoked by uid 22791); 20 Aug 2012 12:31:19 -0000 X-SWARE-Spam-Status: No, hits=-4.9 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mail-ob0-f175.google.com (HELO mail-ob0-f175.google.com) (209.85.214.175) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 20 Aug 2012 12:31:05 +0000 Received: by obc16 with SMTP id 16so10425503obc.20 for ; Mon, 20 Aug 2012 05:31:04 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.52.42 with SMTP id q10mr10305008obo.46.1345465864269; Mon, 20 Aug 2012 05:31:04 -0700 (PDT) Received: by 10.76.9.200 with HTTP; Mon, 20 Aug 2012 05:31:04 -0700 (PDT) In-Reply-To: <1345419449.2268.38.camel@yam-132-YW-E178-FTW> References: <1345337217.2268.2.camel@yam-132-YW-E178-FTW> <1345399738.2268.20.camel@yam-132-YW-E178-FTW> <1345419449.2268.38.camel@yam-132-YW-E178-FTW> Date: Mon, 20 Aug 2012 12:31:00 -0000 Message-ID: Subject: Re: [wwwdocs] SH 4.8 changes update From: Richard Guenther To: Oleg Endo Cc: Gerald Pfeifer , gcc-patches Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org X-SW-Source: 2012-08/txt/msg01339.txt.bz2 On Mon, Aug 20, 2012 at 1:37 AM, Oleg Endo wrote: > On Sun, 2012-08-19 at 21:43 +0200, Gerald Pfeifer wrote: >> On Sun, 19 Aug 2012, Oleg Endo wrote: >> > Thanks. Let's hope that I can squeeze in some more stuff while >> > stage 1 lasts. :T >> >> You know that for backend-specific changes (especially for "smaller" >> ports) you actually have some more leeway? > > You mean, since SH is neither a primary nor a secondary platform, there > are no particular release criteria for it? What does that actually > mean? It means that release managers do not care about the state of the SH port. It means SH target maintainers have to watch how the release goes and decide when to put effort into testing and fixing bugs themselves, otherwise they may run into the situation that the SH port does not even build for the release. So kind of target maintainers for ports that are not primary or secondary are their own release managers without any control over release timing. Richard.