Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] gdbserver 3/3 - new code
Date: Wed, 13 Feb 2002 22:21:00 -0000	[thread overview]
Message-ID: <20020214012115.A2729@nevyn.them.org> (raw)
In-Reply-To: <3C6B3D3B.7020308@cygnus.com>

On Wed, Feb 13, 2002 at 11:29:47PM -0500, Andrew Cagney wrote:
> Only a style nit - wrap the headers in #ifndef #define #endif.  Oh and 
> you're going to have some fun with fnchange.list :-)

Nit noted, will fix before I commit it.  I'm actually not going to have
a problem with fnchange.lst - that's why the files are named
linux-arm-low.c instead of low-linux-arm.c like they used to be.  It
may come up, though :)

I even went through and fixed all the copyright dates I missed the
first time, too.

> The other one is with regformats/*  How sure are you that the regformats 
> so described aren't GNU/Linux (yes check that as well :-) specific?

I tried to verify that all of them were architecture independent.  We
have mechanism in place to cope if I'm wrong; and I can update them to
have comments describing where they are and are not appropriate if we
find somewhere they are not.

I'll scan for GNU/Linux, thanks for the reminder.  One in each
architecture file needed to be fixed.

> If you can add a news entry, I can get the web pages updated.

I'll do that in the next day or two.  Thanks.  Committed otherwise;
tree builds again.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


      reply	other threads:[~2002-02-14  6:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-05 14:56 Daniel Jacobowitz
2002-02-13 20:29 ` Andrew Cagney
2002-02-13 22:21   ` 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=20020214012115.A2729@nevyn.them.org \
    --to=drow@mvista.com \
    --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