public inbox for
help / color / mirror / Atom feed
From: Simon Fowler <>
Subject: Re: insight/186: reggroups.c, reggroups.h not in src/gdb/
Date: Wed, 06 Nov 2002 10:43:00 -0000	[thread overview]
Message-ID: <> (raw)

The following reply was made to PR insight/186; it has been noted by GNATS.

From: Simon Fowler <>
Subject: Re: insight/186: reggroups.c, reggroups.h not in src/gdb/
Date: Thu, 7 Nov 2002 05:34:02 +1100

 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 On Wed, Nov 06, 2002 at 02:17:50PM -0000, wrote:
 > Synopsis: reggroups.c, reggroups.h not in src/gdb/
 > Responsible-Changed-From-To: unassigned->keiths
 > Responsible-Changed-By: kseitz
 > Responsible-Changed-When: Wed Nov  6 06:17:49 2002
 > Responsible-Changed-Why:
 >     mine
 > State-Changed-From-To: open->feedback
 > State-Changed-By: kseitz
 > State-Changed-When: Wed Nov  6 06:17:49 2002
 > State-Changed-Why:
 >     Insight is tightly coupled to the gdb module in U=
 pdating the tree for a checked-out copy of the insight module will get you =
 reggroups.[ch]. I have updated my own sources, and these files certainly sh=
 ow up. Maybe I am not understanding what's going on?
 It was an error on my end - cvs co insight+dejagnu seems to have
 been missing the new files, but manually checking them out worked.
 Not at all sure /why/ it was missing the new files, though . . .
 Sorry for the false alarm.
 PGP public key Id 0x144A991C, or
 (crappy) Homepage:
 doe #237 (see
 My DeCSS mirror:
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 Version: GnuPG v1.2.1 (GNU/Linux)

             reply	other threads:[~2002-11-06 18:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-06 10:43 Simon Fowler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-19 20:08 kseitz
2002-11-06  6:17 kseitz
2002-11-06  4:53 simon

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).