Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Doug Evans <xdje42@gmail.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 03:14:00 -0000	[thread overview]
Message-ID: <20141117031448.GI5774@adacore.com> (raw)
In-Reply-To: <CAP9bCMR7kJi52x+ucwekMet7wkpbZJNBUdc8ktAvQ9sYT5QZaw@mail.gmail.com>

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

Yeah :-( - I think the prefered form is with the (C), and I wish that
it was automatically added during the copyright year update. But,
of course, this is not possible without the script having knowledge
of the file type because it's different for files such as texi files,
for instance. I might write a one-off python script specifically for
that specific purpose, someday....

-- 
Joel


      reply	other threads:[~2014-11-17  3:14 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
2014-11-17  3:14                       ` 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=20141117031448.GI5774@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=xdje42@gmail.com \
    --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