Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <xdje42@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Yao Qi <yao@codesourcery.com>,
		"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH 7/9] Rewrite lookup_static_symbol to use gdbarch routine
Date: Mon, 17 Nov 2014 01:34:00 -0000	[thread overview]
Message-ID: <CAP9bCMR7kJi52x+ucwekMet7wkpbZJNBUdc8ktAvQ9sYT5QZaw@mail.gmail.com> (raw)
In-Reply-To: <CAP9bCMS6+mOMo6Xk8FSRnC43tTc6H+Gg7Lkhwoyu0DJDiUAunA@mail.gmail.com>

On Sun, Nov 16, 2014 at 1:53 PM, Doug Evans <xdje42@gmail.com> wrote:
> On Sat, Nov 15, 2014 at 7:22 PM, Joel Brobecker <brobecker@adacore.com> wrote:
>> Hi Doug,
>>
>>> To keep things moving along I added the copyright headers.
>>
>> Thanks for doing that.
>>
>>> However, I think we could be a bit more lax when it comes to
>>> such trivial testcases.
>>
>> The FSF allows us to be lax for trivial files (with 10 lines being
>> one explicit limit on triviality).  But:
>>
>> The problem with being lax is that it creates a little extra work
>> for us at the start of each year, when we update the copyright headers.
>> The FSF has been asking us to look into copyright headers in the past,
>> and it was a lot of work, so I've added a bit of simple-minded code
>> to the script that updates the copyright headers in GDB to also issue
>> a warning if a copyright header hasn't been found. That way, we can
>> then investigate the few problematic files each year rather than
>> a massive number when the FSF notices something.
>>
>> That's why I always appreciate the copyright headers being added
>> right from the start.
>>
>> So, again, thanks a lot for adding those! :)
>
> No worries.
> A few more words added to the wiki to added the needed context and
> clarity would be great.
> I'll do that.

Hmmm, I see that in gdb the convention is "Copyright (C)" whereas in
the gdb/testsuite the convention is "Copyright" with no "(C)".
Some tests have "(C)" but the vast majority don't.
Both are allowed, and I'm not planning on going through and changing anything.
Just thought I'd point it out.


  reply	other threads:[~2014-11-17  1:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-27  5:01 Doug Evans
2014-10-28  3:16 ` Yao Qi
2014-11-05 20:25   ` Doug Evans
2014-11-07  9:08     ` Doug Evans
2014-11-07 16:29       ` Doug Evans
2014-11-08 19:31         ` Doug Evans
2014-11-11  2:42           ` Doug Evans
2014-11-13 12:52           ` Yao Qi
2014-11-14 17:23             ` Doug Evans
2014-11-15 18:27               ` Doug Evans
2014-11-16  3:22                 ` Joel Brobecker
2014-11-16 21:54                   ` Doug Evans
2014-11-17  1:34                     ` Doug Evans [this message]
2014-11-17  3:14                       ` Joel Brobecker

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=CAP9bCMR7kJi52x+ucwekMet7wkpbZJNBUdc8ktAvQ9sYT5QZaw@mail.gmail.com \
    --to=xdje42@gmail.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=yao@codesourcery.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