From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11117 invoked by alias); 13 Jan 2014 18:44:31 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 11105 invoked by uid 89); 13 Jan 2014 18:44:30 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 13 Jan 2014 18:44:30 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s0DIiQSb025821 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 13 Jan 2014 13:44:26 -0500 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s0DIiOHH000564; Mon, 13 Jan 2014 13:44:25 -0500 Message-ID: <52D43408.404@redhat.com> Date: Mon, 13 Jan 2014 18:44:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 MIME-Version: 1.0 To: Eli Zaretskii CC: brobecker@adacore.com, gdb-patches@sourceware.org Subject: Re: GDB 7.6.90 available for testing References: <20140108101428.C2280E003F@joel.gnat.com> <831u0ec2y6.fsf@gnu.org> <52D427A4.6010704@redhat.com> <83wqi368k7.fsf@gnu.org> In-Reply-To: <83wqi368k7.fsf@gnu.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SW-Source: 2014-01/txt/msg00328.txt.bz2 On 01/13/2014 06:27 PM, Eli Zaretskii wrote: >> Date: Mon, 13 Jan 2014 17:51:32 +0000 >> From: Pedro Alves >> CC: Joel Brobecker , gdb-patches@sourceware.org >> >> On 01/11/2014 08:55 AM, Eli Zaretskii wrote: >> >>> >>> This is because of the "-I./../" part on the GCC command line. My >>> version of GCC doesn't like the trailing slash. >> >> Guessing that's an old gcc. > > Your guess is correct. (I also tried a newer GCC, and the problem > never happened there.) But I think that slash is the odd one out > anyway: the other -I arguments don't have it. > >>> OK to push the following (with a suitable log entry)? >> >> Sure. > > Thanks. > > As this will be my first push when we are branched, what are the > procedures for that with git? I'm guessing > > git checkout gdb-7.7-branch > (hack, hack) > git commit > git push Yeah. As a matter of principle, I prefer fixing master first though, and then backport to any stable branches. So that there's never a chance of the branch getting a fix that's not in mainline (and so the same bug could reappear in mainline later in the next release). (You never know when you might be interrupted, and then forget to merge a change.) > Is that correct? If so, what about doing the same on master -- should > I merge it myself and then push, or are these merges handled in some > other way by someone else? You have to do it yourself. I use stgit, so I just rebase my series on top of master or whatever stable branch, and then push, but with raw git, I'd use git cherry-pick. Thanks, -- Pedro Alves