Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>, gdb-patches@sourceware.org
Subject: Re: [rfc] Remove mips/tm-linux.h
Date: Wed, 16 May 2007 14:09:00 -0000	[thread overview]
Message-ID: <20070516140845.GA24682@caradoc.them.org> (raw)
In-Reply-To: <20070501233716.GA32508@caradoc.them.org>

On Tue, May 01, 2007 at 07:37:16PM -0400, Daniel Jacobowitz wrote:
> > I did run into the that problem on ia64.  That's the reason
> > why I was recently trying to remove the mips-linux NM file,
> > before going after the TM -- but that still isn't quite
> > resolved.
> 
> Thank you!  I hadn't noticed, because I don't generally build native
> mips64-linux debuggers; it was a cross.  I'll be sure not to commit
> this until we resolve that.

Now the NM file is resolved, so I've checked this in to delete the TM
file too.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2007-05-16 14:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-01 20:27 Daniel Jacobowitz
2007-05-01 23:07 ` Ulrich Weigand
2007-05-01 23:37   ` Daniel Jacobowitz
2007-05-16 14:09     ` Daniel Jacobowitz [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=20070516140845.GA24682@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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