Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Daniel Jacobowitz <drow@false.org>,  gdb-patches@sourceware.org
Subject: Re: Ignore two more files for copyright.sh
Date: Tue, 09 Jan 2007 23:31:00 -0000	[thread overview]
Message-ID: <m3wt3vzsiq.fsf@codesourcery.com> (raw)
In-Reply-To: <uzm8rhm3c.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 10 Jan 2007 00:27:51 +0200")


Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Tue, 9 Jan 2007 16:38:11 -0500
>> From: Daniel Jacobowitz <drow@false.org>
>> 
>> Pie on my face.  I knew this would happen... I suppose I'm impressed
>> there was only one test depending on exact line numbering.
>
> Btw, it's possible to have the copyright notice at the end of the
> file, if we say at the beginning something like "Copyright notice at
> the end of the file".  That way, the "operational" parts of the file
> will never change their line numbers, while your script will find the
> copyright if it's within the first 2KB of the file (and if that's not
> enough, we can enlarge this value by a one-line change to the
> gdb-copyright-update function in your script).

There are other facilities in lib/gdb.exp for writing tests so that
they don't depend on exact line numbers (see gdb_get_line_number).
This is a practice to avoid whenever possible, anyway.


  parent reply	other threads:[~2007-01-09 23:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-09 21:38 Daniel Jacobowitz
2007-01-09 22:27 ` Eli Zaretskii
2007-01-09 22:48   ` Daniel Jacobowitz
2007-01-09 23:31   ` Jim Blandy [this message]
2007-01-09 23:37     ` Daniel Jacobowitz
2007-01-09 23:58       ` Jim Blandy
2007-01-10  4:13         ` Eli Zaretskii

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=m3wt3vzsiq.fsf@codesourcery.com \
    --to=jimb@codesourcery.com \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --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