From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 39379 invoked by alias); 14 Jan 2020 13:07:26 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 39347 invoked by uid 89); 14 Jan 2020 13:07:26 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KAM_SHORT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=it!, H*f:sk:87muaqx, H*i:sk:87muaqx, retired X-HELO: mail-wm1-f67.google.com Received: from mail-wm1-f67.google.com (HELO mail-wm1-f67.google.com) (209.85.128.67) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 14 Jan 2020 13:07:15 +0000 Received: by mail-wm1-f67.google.com with SMTP id w5so2269574wmi.1 for ; Tue, 14 Jan 2020 05:07:15 -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=JOmtQEG3b2Ih7nsMXjN9CoQLbq0bv+YYuGjY4LBhLBw=; b=JgyXK3d4xy9PObPkpnwOUD57+RZWcoCGt9shinsYBY6Zz7HaHy9rF70kKr9GGZraVD HS8wW1XJ+EYf95HcCcBi3rCwendnuIq0OPhDO3EMGX93J34ZcqC9uf+RcX2nHcn/hPh1 Mfl3bn9ThO7YiGKOqlPLSy9/99PchL/Z57C2dY3izFqZiWmNUHzMzW19ae/5jRhpXTpH PAhIP629niU0hQUU2pSEp8ZpczCRVmIbmSvVT1ns9jC93R0yIWPSg4HABkI4L8FsvSze WMm9n5R+SRoliRSPulwaPW/buQdrZvv8ahBHOfcqzkNyUdDWM0I8RzzbYgwrmjxZxf24 beww== MIME-Version: 1.0 References: <87muaqxl1e.fsf@igel.home> In-Reply-To: <87muaqxl1e.fsf@igel.home> From: Jonathan Wakely Date: Tue, 14 Jan 2020 14:28:00 -0000 Message-ID: Subject: Re: contrib/gcc_update does not work To: Andreas Schwab Cc: Andrew Pinski , Richard Biener , Uros Bizjak , GCC Development Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2020-01/txt/msg00251.txt.bz2 On Tue, 14 Jan 2020 at 12:46, Andreas Schwab wrote: > > On Jan 14 2020, Andrew Pinski wrote: > > > On Tue, Jan 14, 2020 at 4:10 AM Richard Biener > > wrote: > >> > >> On Tue, Jan 14, 2020 at 11:44 AM Jonathan Wakely wrote: > >> > > >> > On Tue, 14 Jan 2020 at 10:38, Uros Bizjak wrote: > >> > > > >> > > On Tue, Jan 14, 2020 at 11:34 AM Jonathan Wakely wrote: > >> > > > > >> > > > On Tue, 14 Jan 2020 at 09:22, Uros Bizjak wrote: > >> > > > > > >> > > > > gcc_update, when called from newly initialized and pulled tree does not work: > >> > > > > >> > > > Initialized how? > >> > > > >> > > 1035 mkdir gcc > >> > > 1036 cd gcc > >> > > 1037 git init > >> > > 1038 git pull https://gcc.gnu.org/git/gcc.git > >> > > >> > Don't do that :-) > >> > >> I think it's what the wiki still suggests... > > > > Yes the wiki does suggest that but the wiki was about using git mirror. > > Even with the old mirror a normal clone was working as usual. Only if > you wanted to commit using git svn you needed to do the unusual setup. I've added a big bold notice to the top of the wiki page: The information on this page refers to the git-svn mirror WHICH HAS BEEN RETIRED. While some tips here may still be useful (like the convenient git aliases) do not follow these steps to use the new Git repository (which is not a mirror, so obviously this page isn't talking about it!)