Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Remove CLEAR_SOLIB
Date: Wed, 14 Nov 2007 13:20:00 -0000	[thread overview]
Message-ID: <20071114132001.GA7291@caradoc.them.org> (raw)
In-Reply-To: <200711141457.52644.vladimir@codesourcery.com>

On Wed, Nov 14, 2007 at 02:57:52PM +0300, Vladimir Prus wrote:
> 
> It turns out that CLEAR_SOLIB macro is being tested
> for in a couple of places, but it never set anywhere.
> This patch removes all traces of it. OK?

OK.  But really, we ask everyone else to write ChangeLog entries when
they post patches... I'd appreciate if you could too.

While I'm thinking of it I put a helpful script on the Wiki:
  http://sourceware.org/gdb/wiki/Developer_Tips

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-11-14 13:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-14 11:59 Vladimir Prus
2007-11-14 13:20 ` Daniel Jacobowitz [this message]
2007-11-15  6:21   ` Vladimir Prus

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=20071114132001.GA7291@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=vladimir@codesourcery.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