From: Daniel Jacobowitz <drow@false.org>
To: msnyder@sonic.net
Cc: gdb-patches@sourceware.org, gaius@glam.ac.uk
Subject: Re: [RFC] logic change in m2-valprint.c
Date: Tue, 03 Jul 2007 01:24:00 -0000 [thread overview]
Message-ID: <20070703012358.GC27862@caradoc.them.org> (raw)
In-Reply-To: <8387.12.7.175.2.1183425658.squirrel@webmail.sonic.net>
On Mon, Jul 02, 2007 at 06:20:58PM -0700, Michael Snyder wrote:
> You've convinced me -- I don't understand this one.
> I'm going to kick it back to Coverity -- consider this one withdrawn.
Thanks, could you let me know what they say? I can't see the mistake,
but probably it has to do with why they marked empty_set as const...
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-07-03 1:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-29 0:37 msnyder
2007-07-01 15:49 ` Daniel Jacobowitz
2007-07-01 15:54 ` Michael Snyder
2007-07-01 16:03 ` Daniel Jacobowitz
2007-07-03 0:05 ` msnyder
2007-07-03 1:12 ` Daniel Jacobowitz
2007-07-03 1:21 ` msnyder
2007-07-03 1:24 ` Daniel Jacobowitz [this message]
2007-07-03 1:40 ` msnyder
2007-07-03 7:42 ` Mark Kettenis
2007-07-03 19:26 ` Jim Blandy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070703012358.GC27862@caradoc.them.org \
--to=drow@false.org \
--cc=gaius@glam.ac.uk \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@sonic.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox