From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-146895-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 19662 invoked by alias); 28 May 2008 01:11:37 -0000
Received: (qmail 19644 invoked by uid 22791); 28 May 2008 01:11:37 -0000
X-Spam-Check-By: sourceware.org
Received: from wf-out-1314.google.com (HELO wf-out-1314.google.com) (209.85.200.168)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 28 May 2008 01:11:19 +0000
Received: by wf-out-1314.google.com with SMTP id 25so2409407wfc.14         for <gcc@gcc.gnu.org>; Tue, 27 May 2008 18:11:18 -0700 (PDT)
Received: by 10.143.156.15 with SMTP id i15mr788634wfo.4.1211937078159;         Tue, 27 May 2008 18:11:18 -0700 (PDT)
Received: by 10.142.162.18 with HTTP; Tue, 27 May 2008 18:11:18 -0700 (PDT)
Message-ID: <b609cb3b0805271811j4ed63dbje27a1146991d1de5@mail.gmail.com>
Date: Wed, 28 May 2008 01:11:00 -0000
From: NightStrike <nightstrike@gmail.com>
To: "Joe Buck" <Joe.Buck@synopsys.com>
Subject: Re: GCC 4.1 snapshots
Cc: "Richard Guenther" <richard.guenther@gmail.com>,  	"Gerald Pfeifer" <gerald@pfeifer.com>, gcc@gcc.gnu.org
In-Reply-To: <20080527222324.GS23682@synopsys.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <alpine.LSU.1.10.0805272149370.6827@acrux.dbai.tuwien.ac.at> 	 <84fc9c000805271449v61f4c371l16c3ffec20fb4188@mail.gmail.com> 	 <20080527222324.GS23682@synopsys.com>
X-IsSubscribed: yes
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
X-SW-Source: 2008-05/txt/msg00402.txt.bz2

On 5/27/08, Joe Buck <Joe.Buck@synopsys.com> wrote:
> A third alternative is to issue a snapshot (at whatever time interval
> is chosen) iff there's been a checkin on the branch.

I thought that's how it worked already.