From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8641 invoked by alias); 3 Dec 2002 00:58:38 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 8626 invoked from network); 3 Dec 2002 00:58:34 -0000 Received: from unknown (HELO fencepost.gnu.org) (199.232.76.164) by sources.redhat.com with SMTP; 3 Dec 2002 00:58:34 -0000 Received: from monty-python.gnu.org ([199.232.76.173]) by fencepost.gnu.org with esmtp (Exim 4.10) id 18J1OT-0002a1-00 for gcc@gnu.org; Mon, 02 Dec 2002 19:58:33 -0500 Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13) id 18J1OP-000673-00 for gcc@gnu.org; Mon, 02 Dec 2002 19:58:30 -0500 Received: from mail-out1.apple.com ([17.254.0.52]) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18J1OO-00066r-00 for gcc@gnu.org; Mon, 02 Dec 2002 19:58:28 -0500 Received: from mailgate2.apple.com (A17-129-100-225.apple.com [17.129.100.225]) by mail-out1.apple.com (8.11.3/8.11.3) with ESMTP id gB30wSw00997 for ; Mon, 2 Dec 2002 16:58:28 -0800 (PST) Received: from scv2.apple.com (scv2.apple.com) by mailgate2.apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id for ; Mon, 2 Dec 2002 16:58:27 -0800 Received: from bothner.com (il0102b-dhcp138.apple.com [17.201.26.188]) by scv2.apple.com (8.11.3/8.11.3) with ESMTP id gB30wRp09503 for ; Mon, 2 Dec 2002 16:58:27 -0800 (PST) Message-ID: <3DEBFF1F.8070603@bothner.com> Date: Mon, 02 Dec 2002 16:58:00 -0000 From: Per Bothner User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021016 X-Accept-Language: en-us, en MIME-Version: 1.0 To: gcc@gnu.org Subject: gcc branches? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=-2.3 required=5.0 tests=SIGNATURE_SHORT_DENSE,SPAM_PHRASE_00_01,USER_AGENT, USER_AGENT_MOZILLA_UA,X_ACCEPT_LANG version=2.41 X-Spam-Level: X-SW-Source: 2002-12/txt/msg00091.txt.bz2 Any ETA on when the gcc trunk will be open again for non-bug-fixes? I've got two space-reduction patches I'd like to check in soon, and I'm trying to figure out whether to check in to the 3_4-basic-improvements-branch or wait until the trunk is open. Will someone automatically merge in changes from the 3.4 branch into the trunk, or are each of us responsible for our own merges? I hope the former, though if there are any conflicts that may be difficult. -- --Per Bothner per@bothner.com http://www.bothner.com/per/