From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23239 invoked by alias); 3 Dec 2001 19:41: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 23120 invoked from network); 3 Dec 2001 19:41:18 -0000 Received: from unknown (HELO anagyris.wanadoo.fr) (193.252.19.151) by sources.redhat.com with SMTP; 3 Dec 2001 19:41:18 -0000 Received: from citronier.wanadoo.fr (193.252.19.222) by anagyris.wanadoo.fr; 3 Dec 2001 20:41:12 +0100 Received: from ulmo.localdomain (193.251.48.242) by citronier.wanadoo.fr; 3 Dec 2001 20:39:29 +0100 Received: (from guerby@localhost) by ulmo.localdomain (8.11.6/8.11.6) id fB3JWU922496; Mon, 3 Dec 2001 20:32:30 +0100 Date: Mon, 03 Dec 2001 11:41:00 -0000 Message-Id: <200112031932.fB3JWU922496@ulmo.localdomain> X-Authentication-Warning: ulmo.localdomain: guerby set sender to guerby@acm.org using -f From: To: dj@redhat.com CC: gcc@gcc.gnu.org In-reply-to: <200112031657.fB3Gv8a01944@greed.delorie.com> (message from DJ Delorie on Mon, 3 Dec 2001 11:57:08 -0500) Subject: Re: auto-sync of top-level 'include' & 'config' directories? Reply-to: guerby@acm.org References: <200112022321.fB2NLJD29198@ulmo.localdomain> <200112031657.fB3Gv8a01944@greed.delorie.com> X-SW-Source: 2001-12/txt/msg00071.txt.bz2 I don't know what list to contact to relaunch the discussion on what copy of shared file should be the master, feel free to forward extracts of my patches. As for the "shared" directories: config from gcc has mt-alphaieee, config from src has mt-s390pic and mh-s390pic, and include from src has 184 more files than gcc. If there are no strong feelings, what about gcc being the config master and src the include master, with a README.COMMON stating: - patches to include and config must be sent to both xxx-patches mailing lists - approval by an authorized person on one of the projects is enough to commit, if not urgent or new, both approval being better but not required so patches do not stay stuck forever - if there's a problem or conflict about a patch, assume that it can be resolved afterwards by talking - a bot does the sync every hour or so or automatically at commit - if there's a lasting conflict, the bot is extended with code to read gcc/do-not-want-from-src.txt and src/do-not-want-from-gcc.txt and exclude appropriate files from auto-sync so that both project can endlessly flame each other -- Laurent Guerby