From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29231 invoked by alias); 3 Dec 2001 20:40:56 -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 29209 invoked from network); 3 Dec 2001 20:40:49 -0000 Received: from unknown (HELO mel-rti18.wanadoo.fr) (193.252.19.34) by sources.redhat.com with SMTP; 3 Dec 2001 20:40:49 -0000 Received: from amyris.wanadoo.fr (193.252.19.150) by mel-rti18.wanadoo.fr; 3 Dec 2001 21:40:48 +0100 Received: from ulmo.localdomain (193.251.48.242) by amyris.wanadoo.fr; 3 Dec 2001 21:40:05 +0100 Received: (from guerby@localhost) by ulmo.localdomain (8.11.6/8.11.6) id fB3KWtS23248; Mon, 3 Dec 2001 21:32:55 +0100 Date: Mon, 03 Dec 2001 12:40:00 -0000 Message-Id: <200112032032.fB3KWtS23248@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: <200112032021.fB3KLAj06353@greed.delorie.com> (message from DJ Delorie on Mon, 3 Dec 2001 15:21:10 -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> <200112031932.fB3JWU922496@ulmo.localdomain> <200112032021.fB3KLAj06353@greed.delorie.com> X-SW-Source: 2001-12/txt/msg00076.txt.bz2 > Include is not a problem. I've said that MANY times and it hasn't > sunk in yet. The libiberty and include directories are already as > in-sync as they're going to get, and an auto-sync cron job keeps them > that way. Okay sorry for my ignorance, I'm pretty new to all those projects and their common and not-common aspects. To help people that will follow the same path as me, could you put a README.GCC in include and/or libiberty (or wherever is best) documenting the how and why of the current situation? That should take care of the "sunk in yet" for the people that haven't followed in detail a dozen of GNU mailing lists for the past decade, but that do bother reading documentation when it exists and not hidden in a too remote directory :). > > - a bot does the sync every hour or so or automatically at commit > > No. I review every patch before merging, because it's not safe to > truly auto-merge changes that way. Okay so you're the bot :). What about the diff to non doc files I saw? Should I submit a cleaned up patch, if so from what source to what target and to what mailing lists? Or will you take care of that? Thank you for your time, -- Laurent Guerby