Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: David Taylor <dtaylor@usendtaylorx2l.lss.emc.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] PR 17520 -- structure offset wrong when 1/4 GB or greater
Date: Tue, 13 Jan 2015 09:31:00 -0000	[thread overview]
Message-ID: <20150113093056.GD8167@adacore.com> (raw)
In-Reply-To: <19519.1421081631@usendtaylorx2l>

> > Can you add a copyright header to that file, please? All files should
> > have a copyright header unless there is a compelling reason whe cannot
> > add it.
> 
> Done.
> 
> The file is short enough that I'm not sure that it really is
> copyrightable -- but, the lawyers can argue that one, I don't care.

Indeed, some files might be small enough as to not be legally
significant in terms of copyright issues. But rather than introduce
a human decision into the mix, it's just easier to add copyright
headers everywhere. And we have the script which updates all copyright
notices everywhere at the start of the year which tells us if new files
have been introduced without a copyright header.

> I noticed that most of the testsuite *.c files, at least in gdb.base
> do not have copyright notices.

That is a mistake that we should be correcting, but it usually takes
someone seeing the error, then digging through history to figure out
the copyright range, and then adding it.

> I found an example that did something similar to what I wanted and
> copied it.  It had the timeout within the gdb_test_multiple, so that is
> what I did, too.

For TCL, I do the same, but unfortunately, there is a lot of old
baggage, as you've discovered. We try to fix this too, as we see it,
but it's a nearly endless source of work, so progress is usually, er,
slow (understatement).

In case you haven't seen it yet, there is a cookbook:
http://sourceware.org/gdb/wiki/GDBTestcaseCookbook

If some recipes are missing, we'd be glad to add to it.

> I try to do as little as possible in Tcl as every time I do anything
> significant, by the time I'm done I'm remembering just how much I hate
> writing Tcl code.

+1.

-- 
Joel


      reply	other threads:[~2015-01-13  9:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-19  1:54 David Taylor
     [not found] ` <838ui4t3c3.fsf@gnu.org>
2014-12-19 12:40   ` Joel Brobecker
2014-12-20 18:27 ` Joel Brobecker
2015-01-12 16:54   ` David Taylor
2015-01-13  9:31     ` Joel Brobecker [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=20150113093056.GD8167@adacore.com \
    --to=brobecker@adacore.com \
    --cc=dtaylor@usendtaylorx2l.lss.emc.com \
    --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