From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 62356 invoked by alias); 8 Jan 2020 12:48:57 -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 44653 invoked by uid 89); 8 Jan 2020 12:48:45 -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= X-HELO: esa4.mentor.iphmx.com Received: from esa4.mentor.iphmx.com (HELO esa4.mentor.iphmx.com) (68.232.137.252) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 08 Jan 2020 12:48:43 +0000 IronPort-SDR: 2/pEpiH6a+sqAby9r20xKBBsWfyhqg/CB776topU7kJMhHW1mA/TKcdbyKZPBd4TBypSGHXiz6 s2EeZAYt0Tv0wczJXy2i8+1l4EWWtT/12ObC+D09AAVsN1a94QHPlbVDYh+H/9YHQuOje2p9PR MZLc9xc/bs+nt7hnZG3hBhvPdtar41VGyEvLjpzsXU/Yh6Gn84C/f9NcoOYO/p2vMRMwgC1zIy mCYhVdDhiR+9SnQT4/re0AGv423rzbpIM3xih8QxmFLL65AKN+dJiqIBT01c8/l8vyDj+Ka9Yp qiY= Received: from orw-gwy-02-in.mentorg.com ([192.94.38.167]) by esa4.mentor.iphmx.com with ESMTP; 08 Jan 2020 04:48:36 -0800 IronPort-SDR: g133ZNoEkDbTzQs9XYV2CAYhoBH4nAoC2wj8kH/maMt3TroyqT5s/cyKO2QZo5Tox8GGvlfGn+ H50YZhJR8bpUicui7rY7VLwtzIAMIQ2sA/va9/90TP0l/oK5c7qfo7d6wIqDrjQKQZv3wJXAG6 ypyEl7E28Czc0VmYk4gP0q9mqPHrkaVmMnIJrm3jgsCFWVWSJXNUEP0fOi3hA0khONMT3ruMN9 EHKQmppbRs3Qt6k9LNpLShnjQd109DEkdMP2/tD8o5xShWIhebyC0d5wm7oQT5xn7mNZ/SvU/M sSY= Date: Wed, 08 Jan 2020 12:48:00 -0000 From: Joseph Myers To: , Subject: Stopping git-svn updates of GCC git mirror for move to git Message-ID: 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/msg00002.txt For the final conversion of GCC to git we'll need to stop git-svn updates of the existing mirror, which will be moved and replaced with a fresh clean conversion from SVN. Where does the git-svn process updating that mirror run and how can it be disabled at the appropriate time? What I propose is that once the nightly DATESTAMP updates for Saturday have run (shortly after midnight UTC), I check in a README.MOVED_TO_GIT file on SVN trunk, then change the SVN hooks to make the SVN repository readonly. Then, once git-svn has mirrored those changes, the git-svn mirroring should be shut down. I'll set up a pre-receive hook in the mirror to stop further changes being pushed to it, but we don't want git-svn to start trying to push changes to the new repository once that's been moved into place and made writable. -- Joseph S. Myers joseph@codesourcery.com