From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 82856 invoked by alias); 14 Jan 2020 10:34:12 -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 82837 invoked by uid 89); 14 Jan 2020 10:34:12 -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=H*i:sk:fGfeAzw, H*f:sk:fGfeAzw, H*f:sk:CAFULd4, H*i:sk:CAFULd4 X-HELO: mail-wr1-f66.google.com Received: from mail-wr1-f66.google.com (HELO mail-wr1-f66.google.com) (209.85.221.66) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 14 Jan 2020 10:34:02 +0000 Received: by mail-wr1-f66.google.com with SMTP id z7so11560496wrl.13 for ; Tue, 14 Jan 2020 02:34:01 -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=OZVY3/udZkxGuViWCwAeIRoZJbWjrLTCNyJrUxpaJPg=; b=hU2o/60goyis3jYiiaK274gfYire11wx1yP/t0rdXeq9O8LEGM/HgTBiJWgxQ8tnhg InCFsEpgvZSNaSrvvc/FHnPoptNyecG48qdQ+4LLCXm8ncV+ELdqZZG0TlfvVnIM2iCG VjNRqI/Fkli/vhxJ0Su72gX8/6wkxzkNupHWERqc2r3eO4EkW+7702KiWFFK1N46IBUS Eg2GlpDU+kJlIkS1d824UZNknmpW7BOn4iTZ8WV/zfx9ju2huhodOhphly1UMlP8/3Aa wSWhnc8L/a8kvlYmc+/bp2SHsx0CwzdLqpO4xRLOUbwuZGVB1sFNsHxJpnwAOfFunnFI q2kA== MIME-Version: 1.0 References: In-Reply-To: From: Jonathan Wakely Date: Tue, 14 Jan 2020 11:11:00 -0000 Message-ID: Subject: Re: contrib/gcc_update does not work To: Uros Bizjak Cc: GCC Development Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2020-01/txt/msg00233.txt.bz2 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? If you do a 'git clone' then it correctly checks out master and sets it to track origin/master. > > --cut here-- > $ contrib/gcc_update > Updating GIT tree > There is no tracking information for the current branch. > Please specify which branch you want to rebase against. > See git-pull(1) for details. > > git pull > > If you wish to set tracking information for this branch you can do so with: > > git branch --set-upstream-to=origin/ master > > Adjusting file timestamps > git pull of full tree failed. > --cut here-- > > I would also appreciate a simple step-by step instructions on how to > set-up the local repo and basic workflow with git for "non-power" > users, as was the case with now obsolete instructions for anonymous > SVN r/o access [1] and r/w access [2]. Basically, push-my-first-patch > example. > > [1] https://gcc.gnu.org/svn.html > [2] https://gcc.gnu.org/svnwrite.html They're still a work in progress: https://gcc.gnu.org/git.html https://gcc.gnu.org/gitwrite.html