Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH]: MI -var-set-format
Date: Wed, 23 Jan 2008 22:30:00 -0000	[thread overview]
Message-ID: <18327.49121.151323.824267@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20080123212416.GA32524@caradoc.them.org>

 > > I thought the intentio was to commit Vladimir's patch too:
 > > 
 > >   http://sourceware.org/ml/gdb/2008-01/msg00116.html
 > > 
 > > perhaps using xstrdup instead of strdup.  I can then make appropriate
 > > changes to Emacs in the CVS repository prior to the release of 22.2.
 > 
 > One thread at a time is all I can handle.  Have we concluded that the
 > above patch is better than always using natural format to check for
 > updates?

I thought that was part of the thread.  Isn't Marc's patch for
-var-evaluate-expression meant to meet his requirement for multiple formats?

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2008-01-23 22:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-02  6:19 Nick Roberts
2006-05-05 18:11 ` Daniel Jacobowitz
2006-05-05 23:30   ` Nick Roberts
2006-05-15 17:07     ` Daniel Jacobowitz
2006-05-16  3:46       ` Nick Roberts
2008-01-22 20:13         ` Daniel Jacobowitz
2008-01-23  3:25           ` Nick Roberts
2008-01-23  3:48             ` Daniel Jacobowitz
2008-01-23  6:24               ` Nick Roberts
2008-01-23 13:17                 ` Daniel Jacobowitz
2008-01-23 21:17                   ` Nick Roberts
2008-01-23 21:24                     ` Daniel Jacobowitz
2008-01-23 22:30                       ` Nick Roberts [this message]
2008-01-24 21:49 Marc Khouzam
2008-01-25 10:38 ` Eli Zaretskii
2008-01-25 15:46   ` Marc Khouzam

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=18327.49121.151323.824267@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    /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