Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@codesourcery.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Remove deprecated_sym_private
Date: Wed, 03 Feb 2010 17:59:00 -0000	[thread overview]
Message-ID: <20100203175909.GC12046@caradoc.them.org> (raw)
In-Reply-To: <20100203160830.GA83064@ulanbator.act-europe.fr>

On Wed, Feb 03, 2010 at 05:08:30PM +0100, Tristan Gingold wrote:
> Hi,
> 
> I wrote a patch that remove deprecated_sym_private, but I am not sure
> that it is worth applying it: not sure this is a real improvment, and
> I think that the private data_key could be shared among all symbol readers.
> 
> That's the reason why comments are welcome.

Since you've written it, I think it's worth applying it.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2010-02-03 17:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-03 16:08 Tristan Gingold
2010-02-03 17:59 ` Daniel Jacobowitz [this message]
2010-02-03 22:09 ` Tom Tromey
2010-02-05 12:52   ` Tristan Gingold

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=20100203175909.GC12046@caradoc.them.org \
    --to=dan@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=gingold@adacore.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