Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix uninitialized use of variables.
Date: Wed, 24 Oct 2007 17:57:00 -0000	[thread overview]
Message-ID: <20071024172408.GA6387@caradoc.them.org> (raw)
In-Reply-To: <m3y7dstq00.fsf@codesourcery.com>

On Wed, Oct 24, 2007 at 09:51:43AM -0700, Jim Blandy wrote:
> Can you fill us in more on how you'd like remote.c to work?  Maybe we
> can get started, and even get those textual error messages in.

I don't have any bigger picture than I've already said (and I don't
want to pick up a new crusade just now; I am trying to finish the ones
I already have!)

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-10-24 17:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-20 18:07 Carlos O'Donell
2007-10-23 23:20 ` Jim Blandy
2007-10-24 17:24   ` Carlos O'Donell
2007-10-24  0:10 ` Jim Blandy
2007-10-24  4:05   ` Daniel Jacobowitz
2007-10-24 17:12     ` Jim Blandy
2007-10-24 17:57       ` Daniel Jacobowitz [this message]
2007-10-24 17:15   ` Jim Blandy
2007-10-24 18:02   ` Carlos O'Donell
2007-10-24 18:21     ` Jim Blandy
2007-10-26 18:51       ` Carlos O'Donell

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=20071024172408.GA6387@caradoc.them.org \
    --to=drow@false.org \
    --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