From: "Eli Zaretskii" <eliz@gnu.org>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: jimb@redhat.com, cagney@redhat.com, ezannoni@redhat.com,
gdb@sources.redhat.com
Subject: Re: gdb.mi/*.exp and absolute line numbers
Date: Fri, 06 Aug 2004 08:24:00 -0000 [thread overview]
Message-ID: <2914-Fri06Aug2004112150+0300-eliz@gnu.org> (raw)
In-Reply-To: <4111FC04.nailD7G1U3QKS@mindspring.com> (message from Michael Chastain on Thu, 05 Aug 2004 05:21:08 -0400)
> Date: Thu, 05 Aug 2004 05:21:08 -0400
> From: Michael Chastain <mec.gnu@mindspring.com>
>
> So my proposal is:
>
> rewrite gdb_get_line_number in tcl
> (either clone the function or rewrite existing implementation)
> add gdb_get_line_number to gdb.mi/*.exp
> add copyright notices to gdb.mi/{basics.c,gdb701.c,var-cmd.c}
> add #include lines to gdb.mi/{basics.c,gdb701.c,var-cmd.c}
> ... so the the gdb test suite will work with gcc HEAD
>
> Another way out. Less work, but cheesier: put the copyright notices for
> basics.c, gdb701.c, and var-cmd.c in a separate COPYRIGHT file, with a
> note that these files have absolute line numbers and cannot easily be
> edited.
>
> Ideas?
Do we have to put the copyright text at the beginning of a file? If
not, you could add it to the end, which will keep the line info
intact.
But I see you already decided on the first approach.
next prev parent reply other threads:[~2004-08-06 8:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 9:20 Michael Chastain
2004-08-05 13:23 ` Daniel Jacobowitz
2004-08-06 6:26 ` Michael Chastain
2004-08-05 14:34 ` Jim Blandy
2004-08-05 16:02 ` Michael Chastain
2004-08-06 8:24 ` Eli Zaretskii [this message]
2004-08-06 9:41 ` Michael Chastain
2004-08-06 14:46 ` Andrew Cagney
2004-08-06 16:06 ` Michael Chastain
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=2914-Fri06Aug2004112150+0300-eliz@gnu.org \
--to=eliz@gnu.org \
--cc=cagney@redhat.com \
--cc=ezannoni@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=mec.gnu@mindspring.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).