From: Andrew Bennett <Andrew.Bennett@imgtec.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Mike Frysinger <vapier@gentoo.org>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Steve Ellcey <Steve.Ellcey@imgtec.com>
Subject: RE: [PATCH] Add MIPS UFR support
Date: Thu, 19 Dec 2013 10:50:00 -0000 [thread overview]
Message-ID: <0DA23CC379F5F945ACB41CF394B982774E7FCD@LEMAIL01.le.imgtec.org> (raw)
In-Reply-To: <20131219043738.GF3493@adacore.com>
> Hello!
>
> One small request while copyright assignment issues get resolved:
>
>> diff --git a/sim/testsuite/sim/mips/ufr.s b/sim/testsuite/sim/mips/ufr.s
>> new file mode 100644
>> index 0000000..785fefc
>> --- /dev/null
>> +++ b/sim/testsuite/sim/mips/ufr.s
>> @@ -0,0 +1,40 @@
>> +# mips test ufr, expected to pass.
>> +# mach: mips32r2 mips64r2
>> +# as: -mabi=eabi
>
> Every file should have a copyright header in it. The range of years
> for the copyright notice should start with the year the file was
> first committed to a medium, so the year the file was first created.
I am happy to add a copyright header to this file. However, I can only
find three assembler files in the sim/testsuite/sim directory that contain
a copyright header (two of these are mips tests). I was therefore wondering
if it is better to follow the prior art and not contain a header? I don't
know the history here, so would someone be able to advise me?
Many thanks,
Andrew
next prev parent reply other threads:[~2013-12-19 10:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 17:44 Andrew Bennett
2013-11-30 9:59 ` Mike Frysinger
2013-11-30 18:23 ` Maciej W. Rozycki
2013-12-09 16:45 ` Andrew Bennett
2013-12-18 15:36 ` Andrew Bennett
2013-12-18 20:07 ` Mike Frysinger
2013-12-19 17:17 ` Andrew Bennett
2013-12-19 4:37 ` Joel Brobecker
2013-12-19 10:50 ` Andrew Bennett [this message]
2013-12-19 10:59 ` Joel Brobecker
2013-12-19 11:03 ` Andrew Bennett
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=0DA23CC379F5F945ACB41CF394B982774E7FCD@LEMAIL01.le.imgtec.org \
--to=andrew.bennett@imgtec.com \
--cc=Steve.Ellcey@imgtec.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=vapier@gentoo.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