From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-50395-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 32257 invoked by alias); 18 Aug 2007 06:46:46 -0000
Received: (qmail 32108 invoked by uid 22791); 18 Aug 2007 06:46:45 -0000
X-Spam-Check-By: sourceware.org
Received: from nitzan.inter.net.il (HELO nitzan.inter.net.il) (213.8.233.22)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 18 Aug 2007 06:46:42 +0000
Received: from HOME-C4E4A596F7 (IGLD-84-228-240-226.inter.net.il [84.228.240.226]) 	by nitzan.inter.net.il (MOS 3.7.3a-GA) 	with ESMTP id HOL63287 (AUTH halo1); 	Sat, 18 Aug 2007 09:43:52 +0300 (IDT)
Date: Sat, 18 Aug 2007 06:46:00 -0000
Message-Id: <uabspuype.fsf@gnu.org>
From: Eli Zaretskii <eliz@gnu.org>
To: msnyder@sonic.net
CC: gdb-patches@sourceware.org
In-reply-to: <23843.12.7.175.2.1187384595.squirrel@webmail.sonic.net> 	(msnyder@sonic.net)
Subject: Re: NEWS for 6.7: mention coverity bug fixes
Reply-to: Eli Zaretskii <eliz@gnu.org>
References: <10983.12.7.175.2.1187377963.squirrel@webmail.sonic.net>     <ueji1vr7h.fsf@gnu.org> <23843.12.7.175.2.1187384595.squirrel@webmail.sonic.net>
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2007-08/txt/msg00368.txt.bz2

> Date: Fri, 17 Aug 2007 14:03:15 -0700 (PDT)
> From: msnyder@sonic.net
> Cc: msnyder@sonic.net, gdb-patches@sourceware.org
> 
> >> Date: Fri, 17 Aug 2007 12:12:43 -0700 (PDT)
> >> From: msnyder@sonic.net
> >>
> >> Can we include this in 6.7 please?
> >
> > Yes, but...
> >
> >> + * 58 Coverity issues resolved in gdb, 29 in bfd, 1 in libiberty, and
> >> + 1 in opcodes.  These include such things as resource leaks, null
> >> pointer
> >> + dereference, use after free, and array overruns.
> >
> > Are we sure the reader will know what is Coverity, and what does the
> > above mean to her/him?
> 
> I'm open to suggestions.  We could include their URL, for instance...

Yes, and a sentence about what it is.

Or maybe omit the name altogether, and just say that more than 80
issues with resource leaks etc. were resolved.