From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 117282 invoked by alias); 10 Jan 2020 13:29:56 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 117274 invoked by uid 89); 10 Jan 2020 13:29:56 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy= X-HELO: mail-lf1-f45.google.com Received: from mail-lf1-f45.google.com (HELO mail-lf1-f45.google.com) (209.85.167.45) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 10 Jan 2020 13:29:54 +0000 Received: by mail-lf1-f45.google.com with SMTP id r14so1480669lfm.5 for ; Fri, 10 Jan 2020 05:29:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=tJkYWr9HAAWhOY0xqyx098I0v+peZwGbe+74ua9yrlg=; b=lu3zA5Hmzxgh6XVT58RQw7oI1yDRpfE9rlrtN5UEQWpVO/83vX3/X12eF/Y9doIi6g 3b5tN/6TJNATvjIR/s9vbf7VrddkJ/Rxf4fxdlH2P/M/0XJCT4t3UZ/2J0D2JjaPWz08 s1sqi7mUOOV4/6qcfMRVkp3CQt3T1nvXE0aIO1tdiihQ+eTY28ALGC9SBPOiIAuqF7dX 2ALBitiafE/RdFI/5IMajAajeIwumsjCdH96z2ICecx1o7oSuoN1JnKZbZKBzupVLEWr 6fOFecbjP7/V2O0ibg3YtO05xyrX3fA/k/2wwGKhTYg/DG+1XqR0nSHxYU7PwjwjH5gV 0l/g== MIME-Version: 1.0 References: <54834f12-32b1-492f-fb9e-b2c74df23167@arm.com> In-Reply-To: <54834f12-32b1-492f-fb9e-b2c74df23167@arm.com> From: Richard Biener Date: Fri, 10 Jan 2020 13:30:00 -0000 Message-ID: Subject: Re: Some local customization enhancements when using git To: "Richard Earnshaw (lists)" Cc: "gcc-patches@gcc.gnu.org" Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2020-01/txt/msg00543.txt.bz2 On Fri, Jan 10, 2020 at 2:23 PM Richard Earnshaw (lists) wrote: > > This patch is intended to help with folks setting up a git work > environment for use with GCC following the transition to git. It > currently does a couple of things. > > 1) Add an alias 'svn-rev' to git so that you can look up a legacy commit > by its svn revision number. This enables you to type > git svn-rev 1234 > and git will show the commit log entry relating to SVN r1234. > > 2) Sets up tracking information for the user's private name area in the > git repo. It tries to figure out some sensible answers to the data it > needs, but allows the user to override the values. It then creates the > fetch and push entries that are needed for tracking the extra refs. > This implements one part of the recommendations that I've proposed in > svnwrite.html for dealing with private branches. > > It should be possible to run the script more than once and for it to > DTRT. If you change your answers the configuration should be correctly > updated. I assume the script is invoked from a clone of the new (final) repo. Does it need to be cloned in any special way? Richard. > 2020-01-10 Richard Earnshaw > > * gcc-git-customization: New file. >