From: Pedro Alves <palves@redhat.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>,
"Aktemur, Tankut Baris" <tankut.baris.aktemur@intel.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] gdbserver: Add .dir-locals.el file
Date: Mon, 02 Mar 2020 14:05:00 -0000 [thread overview]
Message-ID: <d9ed874a-67a7-6312-4157-4c36aae83ee7@redhat.com> (raw)
In-Reply-To: <20200302120208.GP3317@embecosm.com>
On 3/2/20 12:02 PM, Andrew Burgess wrote:
>>> +;; Copyright (C) 2012-2020 Free Software Foundation, Inc.
>>
>> ... and I think they year needs to be just '2020'.
>
> As per this rule:
>
> https://sourceware.org/gdb/wiki/ContributionChecklist#Copyright_Header
>
> When copying a file the start date of the original file should be
> maintained I think.
Yes, otherwise we could put just "2020" everywhere using this:
$ cp org.c new.c
# I have a new file, so let me update copyright to 2020:
$ sed s/20*-2020/2020/g -i new.c
# Rename the new file back to the old name:
$ mv new.c org.c
Copyright covers the code, the file's content, not the file name.
Pedro Alves
prev parent reply other threads:[~2020-03-02 14:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 9:53 Andrew Burgess
2020-03-02 10:17 ` Aktemur, Tankut Baris
2020-03-02 12:31 ` [PATCHv2] " Andrew Burgess
2020-03-02 14:06 ` Pedro Alves
2020-03-02 17:08 ` Andrew Burgess
2020-03-02 17:34 ` Pedro Alves
2020-03-02 17:58 ` Eli Zaretskii
2020-03-02 18:13 ` Pedro Alves
2020-03-02 19:19 ` Eli Zaretskii
[not found] ` <20200305151232.GB3317@embecosm.com>
2020-03-05 15:26 ` Eli Zaretskii
2020-03-05 16:00 ` Pedro Alves
[not found] ` <BYAPR11MB3030342645BFA8E7610CF862C4E70@BYAPR11MB3030.namprd11.prod.outlook.com>
2020-03-02 12:02 ` [PATCH] " Andrew Burgess
2020-03-02 14:05 ` Pedro Alves [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=d9ed874a-67a7-6312-4157-4c36aae83ee7@redhat.com \
--to=palves@redhat.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=tankut.baris.aktemur@intel.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