From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-patches-return-366764-listarch-gcc-patches=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 16019 invoked by alias); 7 May 2014 09:40:26 -0000
Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-patches.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-patches/>
List-Post: <mailto:gcc-patches@gcc.gnu.org>
List-Help: <mailto:gcc-patches-help@gcc.gnu.org>
Sender: gcc-patches-owner@gcc.gnu.org
Received: (qmail 16008 invoked by uid 89); 7 May 2014 09:40:25 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO: mail-qc0-f171.google.com
Received: from mail-qc0-f171.google.com (HELO mail-qc0-f171.google.com) (209.85.216.171) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Wed, 07 May 2014 09:40:24 +0000
Received: by mail-qc0-f171.google.com with SMTP id x13so763479qcv.2        for <gcc-patches@gcc.gnu.org>; Wed, 07 May 2014 02:40:22 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20130820;        h=x-gm-message-state:mime-version:in-reply-to:references:date         :message-id:subject:from:to:cc:content-type;        bh=GLkvDMGoUY8tWKWa0WYulJjWuWC8VLFkx4dhhqXKnrM=;        b=mbG+lDAyQyFWT8p81zo/nGebqNvAkT0kt9jR6/YWMay4k65PB26UDCGcCWICYAVGpA         /QO1K28XlpTvkBZgxsg5ik6kLEW+2y7D9G0SlcsgIYaUZW0OdSr1S9OKUkFCAkDnVPME         xsNuW83QW6Z5C16JbQ9FfpH3KkiLSjgW/v4ynxWV9N9SAeVMXYT7xH04EGFV0lHYCH9p         qeRuHX7W+yFi1CHqPN5NRcuPNeo16SPoZPx4UXjd/kCy+AoUwGJdAHhyKYjN80bF38Rg         CimsogsNHD+lmmtQHwWGZgqXaJxIpTI/S4rem8SfXMtX+8XZB19dAJM8acqM2LUYpBBG         92Cg==
X-Gm-Message-State: ALoCoQmJMLDmlg/2SFt9R9EPq3pydgPvEHeXjITLpj1kXkLJUbtcY3CGN+4qWJ7uKmi/tU3QsnGo
MIME-Version: 1.0
X-Received: by 10.140.89.18 with SMTP id u18mr57880623qgd.78.1399455622492; Wed, 07 May 2014 02:40:22 -0700 (PDT)
Received: by 10.140.103.180 with HTTP; Wed, 7 May 2014 02:40:22 -0700 (PDT)
In-Reply-To: <mvmtx92yqpf.fsf@hawking.suse.de>
References: <5368FD99.2010607@naturalbridge.com>	<A41D2B7B-480F-475B-B1CB-9FD001F5622C@comcast.net>	<20140506211747.GJ31532@lug-owl.de>	<CAKdteOZUCrw6btC9s2+MhLz-qCWKM341sxzQURGc+NL6mju5Gg@mail.gmail.com>	<mvmtx92yqpf.fsf@hawking.suse.de>
Date: Wed, 07 May 2014 09:40:00 -0000
Message-ID: <CAKdteOZkJaQTJFLnQpqJ1JqPSwUwDOb0-Ygvudvzu8eidUCXCQ@mail.gmail.com>
Subject: Re: we are starting the wide int merge
From: Christophe Lyon <christophe.lyon@linaro.org>
To: Andreas Schwab <schwab@suse.de>
Cc: Jan-Benedict Glaw <jbglaw@lug-owl.de>, Mike Stump <mikestump@comcast.net>, 	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes
X-SW-Source: 2014-05/txt/msg00379.txt.bz2

On 7 May 2014 09:48, Andreas Schwab <schwab@suse.de> wrote:
> Christophe Lyon <christophe.lyon@linaro.org> writes:
>
>> It also looks like the git-svn-id property is now wrong/incomplete.
>> For instance, commit 9a5942c1d4d9116ab74b0741cfe3894a89fd17fb has:
>>     git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/branches/wide-int@201706
>> 138bc75d-0d04-0410-961f-82ee72b054a4
>>
>> How does it map to the SVN commit in trunk?
>
> This is a commit on the wide-int branch (the one that created it).
>

I had a bug in my script while parsing the output of git log,
hopefully fixed now.