From: Andrew Cagney <ac131313@redhat.com>
To: David Carlton <carlton@kealia.com>
Cc: insight@sources.redhat.com
Subject: Re: [patch] REGISTER_RAW_SIZE => DEPRECATED_REGISTER_RAW_SIZE
Date: Mon, 06 Oct 2003 18:30:00 -0000 [thread overview]
Message-ID: <3F81B4D5.90003@redhat.com> (raw)
In-Reply-To: <yf23ce6ba0z.fsf@hawaii.kealia.com>
> Andrew's latest deprecation missed occurrences in insight. Andrew,
> can you please test these patches on a tree containing insight? And
> if the insight people were to get around to making it possible to
> build GDB in a tree containing insight, even if there are compilation
> problems on the insight side, that would be greatly appreciated as
> well.
Don't forget that Insight isn't part of GDB so there's no obligation on
the part of GDB's FSF maintainers - you included - to keep Insight
building. I do it if I remember. However, I don't do it by default as
it adds a significant drain to my volunteer FSF time.
Perhaphs Red Hat will finally contribute Insight to the FSF?
Andrew
next prev parent reply other threads:[~2003-10-06 18:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-06 16:34 David Carlton
2003-10-06 18:30 ` Andrew Cagney [this message]
2003-10-06 19:49 ` David Carlton
2003-10-06 21:24 ` Andrew Cagney
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=3F81B4D5.90003@redhat.com \
--to=ac131313@redhat.com \
--cc=carlton@kealia.com \
--cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).