From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 40908 invoked by alias); 26 May 2017 17:43:01 -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 40305 invoked by uid 89); 26 May 2017 17:42:59 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=unavailable version=3.3.2 spammy=act, our X-HELO: eggs.gnu.org Received: from eggs.gnu.org (HELO eggs.gnu.org) (208.118.235.92) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 26 May 2017 17:42:56 +0000 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dEJGJ-0003FE-Jf for gdb-patches@sourceware.org; Fri, 26 May 2017 13:42:58 -0400 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:47638) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dEJGJ-0003F1-GJ; Fri, 26 May 2017 13:42:55 -0400 Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:1222 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1dEJGI-0005oT-EK; Fri, 26 May 2017 13:42:54 -0400 Date: Fri, 26 May 2017 17:43:00 -0000 Message-Id: <834lw7jyzn.fsf@gnu.org> From: Eli Zaretskii To: Joel Brobecker CC: dj@redhat.com, gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org In-reply-to: <20170526163053.aj22jelqmoeo7wvd@adacore.com> (message from Joel Brobecker on Fri, 26 May 2017 09:30:53 -0700) Subject: Re: MinGW compilation warnings in libiberty's waitpid.c Reply-to: Eli Zaretskii References: <83poewjb08.fsf@gnu.org> <20170526163053.aj22jelqmoeo7wvd@adacore.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-IsSubscribed: yes X-SW-Source: 2017-05/txt/msg00571.txt.bz2 > Date: Fri, 26 May 2017 09:30:53 -0700 > From: Joel Brobecker > Cc: DJ Delorie , gcc-patches@gcc.gnu.org, > gdb-patches@sourceware.org > > Normally, I'd expect someone pushing to GCC's libibert to also > update our repo accordingly. However, it's easy to forget so, > if you notice a change that was not propagated to us, we just > cherry-pick those changes so as to make sure our copy is up > to date with GCC's. We also see the occasional "resync libiberty" > commits which act as a failsafe, but I don't think we should wait > for one of those. What can I do to expedite the process? This currently holds the 8.0 release, and I'm uneasy to be the culprit. > Should those ones be pushed to the gdb-8.0-branch as well? Yes.