From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 84452 invoked by alias); 26 May 2017 22:02:26 -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 84402 invoked by uid 89); 26 May 2017 22:02:25 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy= X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 26 May 2017 22:02:24 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id B1450F5EBC; Fri, 26 May 2017 18:02:26 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id RPidpCQf+Cts; Fri, 26 May 2017 18:02:26 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 860EFB6715; Fri, 26 May 2017 18:02:26 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id AA3FA803A2; Fri, 26 May 2017 15:02:23 -0700 (PDT) Date: Fri, 26 May 2017 22:02:00 -0000 From: Joel Brobecker To: Eli Zaretskii Cc: dj@redhat.com, gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org Subject: Re: MinGW compilation warnings in libiberty's waitpid.c Message-ID: <20170526220223.pck2acjf2fhengzb@adacore.com> References: <83poewjb08.fsf@gnu.org> <20170526163053.aj22jelqmoeo7wvd@adacore.com> <834lw7jyzn.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <834lw7jyzn.fsf@gnu.org> User-Agent: NeoMutt/20170113 (1.7.2) X-SW-Source: 2017-05/txt/msg00586.txt.bz2 > What can I do to expedite the process? This currently holds the 8.0 > release, and I'm uneasy to be the culprit. The way I usually do it is grab the commit in GCC, and apply it as is in the GDB repository. To make it easier, I use the git mirror of the GCC repository, because I can then just add the GCC repository as one of my remotes, fetch from there, and then cherry-pick. If you prefer to work from GCC's SVN repository, just use SVN to get the diff, and re-apply it by hand in GDB's git repository. The advantage with the cherry-pick is that git does nearly all of the work (revision log, etc). -- Joel