From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-201230-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 9011 invoked by alias); 27 Dec 2019 13:35:21 -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 9001 invoked by uid 89); 27 Dec 2019 13:35:21 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy=Which, H*i:sk:XsRDMQa, H*i:sk:Sn1nhRq, H*f:sk:XsRDMQa
X-HELO: gate.crashing.org
Received: from gate.crashing.org (HELO gate.crashing.org) (63.228.1.57) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 27 Dec 2019 13:35:20 +0000
Received: from gate.crashing.org (localhost.localdomain [127.0.0.1])	by gate.crashing.org (8.14.1/8.14.1) with ESMTP id xBRDZF86011345;	Fri, 27 Dec 2019 07:35:15 -0600
Received: (from segher@localhost)	by gate.crashing.org (8.14.1/8.14.1/Submit) id xBRDZEN4011343;	Fri, 27 Dec 2019 07:35:14 -0600
Date: Fri, 27 Dec 2019 13:35:00 -0000
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Andrew Pinski <pinskia@gmail.com>
Cc: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>,        Joseph Myers <jsm@polyomino.org.uk>, Jakub Jelinek <jakub@redhat.com>,        Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>,        GCC Development <gcc@gcc.gnu.org>, Alexandre Oliva <oliva@gnu.org>,        "Eric S. Raymond" <esr@thyrsus.com>, Jeff Law <law@redhat.com>,        Mark Wielaard <mark@klomp.org>
Subject: Re: Proposal for the transition timetable for the move to GIT
Message-ID: <20191227133514.GR4505@gate.crashing.org>
References: <20191225120747.GA96669@thyrsus.com> <orh81n1uv0.fsf@livre.home> <alpine.DEB.2.21.1912261054320.27097@digraph.polyomino.org.uk> <20191226111633.GJ10088@tucnak> <5DCEA32B-3E36-4400-B931-9F4E2A8F3FA5@linaro.org> <alpine.DEB.2.21.1912261632130.28986@digraph.polyomino.org.uk> <20191226183553.GK10088@tucnak> <alpine.DEB.2.21.1912261858420.30156@digraph.polyomino.org.uk> <d9a8603d-f59e-beeb-508a-807f78f9e126@arm.com> <CA+=Sn1nhRqttzV3xvtwEnZ+XsRDMQaFvPqQsH14m1w_JUgqvpA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CA+=Sn1nhRqttzV3xvtwEnZ+XsRDMQaFvPqQsH14m1w_JUgqvpA@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
X-IsSubscribed: yes
X-SW-Source: 2019-12/txt/msg00448.txt.bz2

On Fri, Dec 27, 2019 at 03:32:57AM -0800, Andrew Pinski wrote:
> The one branch merge which would have helped me track down why a
> testcase was added is the tree-ssa branch merge.  If we had the commit
> for the merge to have the merge info, it would have been easier for me
> to track down that.  Note this testcase failed with a new patch I am
> working on and I decided in the end, the testcase is bogus and not
> even testing what it was testing for anyways.  There is a few other
> instances like that which would have been helpful.

It sounds like it would have helped you if the testcase had stated what
it is for, what it is testing, in the testcase file itself.  As all tests
should, imnsho.

In the more general case you need to find the discussion on the mailing
list archives.  Which is a difficul problem in itself.


Segher