From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 79170 invoked by alias); 19 May 2017 17:55:57 -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 79152 invoked by uid 89); 19 May 2017 17:55:56 -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=ham version=3.3.2 spammy=HTo:U*dj, week!, 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, 19 May 2017 17:55:54 +0000 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dBm7z-00047g-Er for gdb-patches@sourceware.org; Fri, 19 May 2017 13:55:55 -0400 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:32946) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dBm7z-00047c-Ax; Fri, 19 May 2017 13:55:51 -0400 Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:4374 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1dBm7y-0008T5-Fh; Fri, 19 May 2017 13:55:50 -0400 Date: Fri, 19 May 2017 17:55:00 -0000 Message-Id: <834lwg3f55.fsf@gnu.org> From: Eli Zaretskii To: DJ Delorie CC: brobecker@adacore.com, qiyaoltc@gmail.com, gdb-patches@sourceware.org In-reply-to: (message from DJ Delorie on Fri, 19 May 2017 13:50:41 -0400) Subject: Re: GDB 7.99.91 MinGW compilation warning in tui.c Reply-to: Eli Zaretskii References: 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/msg00466.txt.bz2 > From: DJ Delorie > Cc: brobecker@adacore.com, qiyaoltc@gmail.com, gdb-patches@sourceware.org > Date: Fri, 19 May 2017 13:50:41 -0400 > > Eli Zaretskii writes: > > Btw, what should I do about the issues I reported against libiberty? > > I got no responses for my reports. Should I just go ahead and fix our > > copy of libiberty? > > They're on my list, just had a busy week! Sorry for my impatience, and thanks in advance.