From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3011 invoked by alias); 8 Jan 2020 13:22:15 -0000 Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org Received: (qmail 3003 invoked by uid 89); 8 Jan 2020 13:22:15 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=online X-HELO: esa1.mentor.iphmx.com Received: from esa1.mentor.iphmx.com (HELO esa1.mentor.iphmx.com) (68.232.129.153) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 08 Jan 2020 13:22:14 +0000 IronPort-SDR: jfX/Q4uuO5TJv0fwNMbV8BLsztPsWuztW/v9TZdODpNL3NjP/buB1CLJKvaLEWX6t/uwxYMbsX DyhG1GSKfk9qYfnYKoPbVt2f5RJ+CFAF/7qbqntUikAoPgwXcGXGmFBhm1Qj7UMN0V5nSuZxS4 VLX9oB+WErKDNBVvkFvOv6DsNmn3PPO90ODNaKeV8BH6EWynbVnSVDIjwwEnDaOVkq2s2KEMrg dDL8Hv0heIvhNs4NelJTFbxWW0cBjy8a0fsheJlnTtjZqt1HtOmwfPpThmqRfsS1MzcTuOogu7 y2I= Received: from orw-gwy-02-in.mentorg.com ([192.94.38.167]) by esa1.mentor.iphmx.com with ESMTP; 08 Jan 2020 05:22:12 -0800 IronPort-SDR: Tp9L5HmLAqzheNOI37rNOBhmFqsazlPYRWLy9sYwLn2Ar/iHFPimHmEs1Kp3xPSB7pcVxHXjwR luj7KJ/Y7leHn0WFMS2Nn/QEM+KugDsHwc/mlRK5BE0cHnGz0L3h6XZuNxwh8wGxaqqfG82Hy0 aBf9dXpkJoYhEw5bW8pIYicEIzfcMEQCRje532rzK5HtiGoZDWYhxF212YMhEWg5WIubFzjmus 1NcxlE2h/vsouT8BuRyKpH97DNkte5J/23gFi8848kkf6byYcq1ypXTfI3dboZZIZsMAdKT06A kYc= Date: Wed, 08 Jan 2020 13:22:00 -0000 From: Joseph Myers To: "Frank Ch. Eigler" CC: , Subject: Re: Stopping git-svn updates of GCC git mirror for move to git In-Reply-To: <20200108131358.GB13316@redhat.com> Message-ID: References: <20200108131358.GB13316@redhat.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Return-Path: joseph@codesourcery.com X-SW-Source: 2020-q1/txt/msg00004.txt On Wed, 8 Jan 2020, Frank Ch. Eigler wrote: > Hi - > > > [...] Where does the git-svn process updating that mirror run and > > how can it be disabled at the appropriate time? [...] > > I believe all of the gcc-svn automation is run out of cron jobs owned > by the gccadmin user, via scripts in /home/gccadmin/scripts/. It's > not something set up or overseen by the overseers. Let us know if you > need us to perform any unusual protective measures around the > transition time, beyond the routine backups etc. already going. No, git-svn isn't run there. The snapshots, DATESTAMP updates and online documentation updates are run from there, and I'll disable them in the crontab at the appropriate point and then re-enable them once converted to work with git, but git-svn is run from somewhere else (possibly by Jason?). Could you (now) set up a symlink /git/gcc-old.git -> /sourceware/projects/gcc-home/gitfiles-old ? Right now gitfiles-old is a symlink to gitfiles that I just created, but at an appropriate point I'll move gitfiles to gitfiles-old (so gcc-old.git will be the location people use if they want to check out the old mirror after that) and put the newly converted repository at gitfiles (so gcc.git remains the main path to the main git repository for GCC). -- Joseph S. Myers joseph@codesourcery.com