Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: fix PR 9350
Date: Thu, 08 Jan 2009 16:33:00 -0000	[thread overview]
Message-ID: <m3y6xl21xh.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20090108092722.GO3664@adacore.com> (Joel Brobecker's message of "Thu\, 8 Jan 2009 13\:27\:22 +0400")

>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:

Joel> I did noticed that a patch to value.c disappeared compared to
Joel> the initial patch. But it looks like it's been taken care of
Joel> already, so all is well.

Yeah, that was a separate patch that I put in my working tree during
testing to make sure valgrind was quiet.  I forgot to remove it before
making the patch I sent to gdb-patches.  Sorry about that.

I've committed the patch.

Tom


      reply	other threads:[~2009-01-08 16:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-07  1:08 Tom Tromey
2009-01-07  8:35 ` Joel Brobecker
2009-01-07 14:49   ` Tom Tromey
2009-01-07 16:18     ` Tom Tromey
2009-01-08  9:27       ` Joel Brobecker
2009-01-08 16:33         ` Tom Tromey [this message]

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=m3y6xl21xh.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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