From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-201574-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 103891 invoked by alias); 14 Jan 2020 12:10:03 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 103882 invoked by uid 89); 14 Jan 2020 12:10:03 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KAM_SHORT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=ubizjak@gmail.com, ubizjakgmailcom, H*i:sk:ewFPscQ, H*f:sk:ewFPscQ
X-HELO: mail-lj1-f193.google.com
Received: from mail-lj1-f193.google.com (HELO mail-lj1-f193.google.com) (209.85.208.193) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 14 Jan 2020 12:09:53 +0000
Received: by mail-lj1-f193.google.com with SMTP id z22so14075714ljg.1        for <gcc@gcc.gnu.org>; Tue, 14 Jan 2020 04:09:52 -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=0pbc/bXrWdgD1GTP4OCvcMxGUYVS9xmAbZR66+OChkQ=;        b=rtLjNbDXBb2/+tHim+J8QFW6j5tlW+mLgyY3CbQcms4y23Z1wZOq8sN0Eqv941sARs         qkYo7aPQxTD4mCe2BcEtj4UZjI08Ja1RZMLh/bwl0pnLhnZwmS2osLaEweIdd5xTr7H5         zCcVO0aguTUr/DwlMEm7HbdIDiapiscxHmLlYWfKY4e0/83BlTV28Kcc+ybZRjxGYkym         EOxJPkfekVv2PRjqXb2dmNAeNQoICvT/luFYq4EFl533KSRsqX87Suz6PrA8HurN4LFo         wV3KDPufrw3D41BqEAvbiCzFHOunJV6OeGrF7SjyWV4i3oLfJXf55O+cpIXVp3D6z/OW         p0Sg==
MIME-Version: 1.0
References: <CAFULd4Zs9HcToGd4+fGfeAzwA_MNoykso5OX9rC9nVDrzWo2OA@mail.gmail.com> <CAH6eHdTBHdNs8CM86dYuBKsCCGe73EnwxPdA-uDBpAx77Hww3A@mail.gmail.com> <CAFULd4bqNiumLAVHXBV3wOoVZU+at+wXbnv3V_z0B4J1Rj4T-Q@mail.gmail.com> <CAH6eHdTyr6GcAa_oiKcwteZdmJ_rT9Ujkg1_0YYH1z+ewFPscQ@mail.gmail.com>
In-Reply-To: <CAH6eHdTyr6GcAa_oiKcwteZdmJ_rT9Ujkg1_0YYH1z+ewFPscQ@mail.gmail.com>
From: Richard Biener <richard.guenther@gmail.com>
Date: Tue, 14 Jan 2020 12:58:00 -0000
Message-ID: <CAFiYyc3mMcOPc_oyW4J7R64BZLv1FTTund6_ucGfdzVF7cOM6A@mail.gmail.com>
Subject: Re: contrib/gcc_update does not work
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Uros Bizjak <ubizjak@gmail.com>, GCC Development <gcc@gcc.gnu.org>
Content-Type: text/plain; charset="UTF-8"
X-IsSubscribed: yes
X-SW-Source: 2020-01/txt/msg00244.txt.bz2

On Tue, Jan 14, 2020 at 11:44 AM Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
>
> On Tue, 14 Jan 2020 at 10:38, Uros Bizjak <ubizjak@gmail.com> wrote:
> >
> > On Tue, Jan 14, 2020 at 11:34 AM Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> > >
> > > On Tue, 14 Jan 2020 at 09:22, Uros Bizjak <ubizjak@gmail.com> 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...

> You've created an new, empty repository and then filled it with the
> content from gcc.gnu.org/git/gcc but that's not the same as making a
> clone of that repo. You could make it the same, but you'd have to do a
> lot more steps manually. Just use 'git clone'.
>
> > > If you do a 'git clone' then it correctly checks out master and sets
> > > it to track origin/master.
> >
> > I see, I'll try this now.