From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16401 invoked by alias); 8 Mar 2004 19:34:28 -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 16386 invoked from network); 8 Mar 2004 19:34:21 -0000 Received: from unknown (HELO vexpert.dbai.tuwien.ac.at) (128.131.111.2) by sources.redhat.com with SMTP; 8 Mar 2004 19:34:21 -0000 Received: from [128.131.111.60] (acrux [128.131.111.60]) by vexpert.dbai.tuwien.ac.at (Postfix) with ESMTP id C384513795; Mon, 8 Mar 2004 20:34:15 +0100 (CET) Date: Mon, 08 Mar 2004 19:34:00 -0000 From: Gerald Pfeifer To: Ranjit Mathew Cc: gcc@gcc.gnu.org Subject: Re: 3.5 Snapshots (Again) In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2004-03/txt/msg00399.txt.bz2 On Mon, 8 Mar 2004, Ranjit Mathew wrote: > The last time this issue was raised by Kelly Cook nothing happened, so > I'm raising this yet again: can we please start having 3.5 snapshots? First we need some infrastructure changes to get the diffs right, that's the major blocker right now. I'll try to work on that tonight. > The policy should be to publish snapshots from the current development > tree (mainline) and the current release tree - as I said before, I don't > think there are hordes of hackers just waiting for their weekly 3.3 > snapshots at this point. Snapshots are not just used by hacker, but also by the FreeBSD system and probably other as well. And there are quite few hackers which do not have CVS access. In fact, it is hardly possible to contribute code to GCC with only snapshot access, as one cannot do proper testing. Gerald