Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: gdb-patches@sourceware.org
Subject: Re: [commit] Clean up proc-service includes in gdbserver
Date: Wed, 15 Mar 2006 22:39:00 -0000	[thread overview]
Message-ID: <200603152227.k2FMRrlY006031@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20060315161633.GA15527@nevyn.them.org> (message from Daniel 	Jacobowitz on Wed, 15 Mar 2006 11:16:33 -0500)

> Date: Wed, 15 Mar 2006 11:16:33 -0500
> From: Daniel Jacobowitz <drow@false.org>
> 
> A while ago, I posted MIPS and ARM NPTL support for gdbserver.
> Before I got around to checking it in, Mark K. looked at one of
> them and went "ewwww..."; it was just copied from three other places
> in gdbserver, but I totally agree with his reaction.  So this patch
> un-ewwws things a bit.  Instead of borrowing gdb_proc_service.h
> from gdb, this patch gives gdbserver its own, slightly different
> copy.

Heh, thanks.  This certainly looks like an improvement!

Mark


      parent reply	other threads:[~2006-03-15 22:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-15 16:36 Daniel Jacobowitz
2006-03-15 22:28 ` Michael Snyder
2006-03-15 22:36   ` Daniel Jacobowitz
2006-03-15 22:39 ` Mark Kettenis [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=200603152227.k2FMRrlY006031@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --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