From: Doug Evans <xdje42@gmail.com>
To: Yao Qi <yao@codesourcery.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH 7/9] Rewrite lookup_static_symbol to use gdbarch routine
Date: Fri, 14 Nov 2014 17:23:00 -0000 [thread overview]
Message-ID: <CAP9bCMQEbfjt2N+qgzt-NXh27T+Gsa7i8cOCfoZ28EL-jfTbmA@mail.gmail.com> (raw)
In-Reply-To: <87y4rfjm9h.fsf@codesourcery.com>
On Thu, Nov 13, 2014 at 4:52 AM, Yao Qi <yao@codesourcery.com> wrote:
> Doug Evans <xdje42@gmail.com> writes:
>
> Hi Doug,
> Sorry for the delayed response.
>
>> 2014-11-08 Doug Evans <xdje42@gmail.com>
>>
>> PR symtab/17564
>> * gdb.base/symtab-search-order.exp: New file.
>> * gdb.base/symtab-search-order.c: New file.
>> * gdb.base/symtab-search-order-1.c: New file.
>> * gdb.base/symtab-search-order-shlib-1.c: New file.
>
> These new .c files need copyright headers.
These files are so trivial, I left them out.
[The .exp file *does* have a copyright header.]
I know the contribution checklist page mentions always adding them,
even if the GNU standards only require them for legally significant
headers.
It's not clear that that is intended to apply in particular cases such as these.
[I can add them, but establishing some clarity would be nice.]
next prev parent reply other threads:[~2014-11-14 17:23 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 [this message]
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
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=CAP9bCMQEbfjt2N+qgzt-NXh27T+Gsa7i8cOCfoZ28EL-jfTbmA@mail.gmail.com \
--to=xdje42@gmail.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