Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Doug Evans <dje@sebabeach.org>, gdb-patches@sourceware.org
Subject: Re: [patch] Create cleanups.[ch]
Date: Wed, 18 Apr 2012 09:43:00 -0000	[thread overview]
Message-ID: <4F8E8A37.6070900@redhat.com> (raw)
In-Reply-To: <m3aa2bjyt0.fsf@redhat.com>

On 04/16/2012 07:50 PM, Sergio Durigan Junior wrote:

> On Monday, April 16 2012, Pedro Alves wrote:
> 
>> On 04/16/2012 06:00 AM, Sergio Durigan Junior wrote:
>>> It should be:
>>
>>>
>>> Copyright (C) 2012 Free Software Foundation, Inc.
>>>
>>> AFAIK, since it's a new file.
>>
>>
>> But the contents are not new.  By that reasoning, if we renamed
>> every file in the tree, while changing nothing else, all the copyright
>> years would end up 2012 only.  I don't think that'd be right.
> 
> I always thought that the Copyright referred to the file itself, so if
> you create a new file you should "restart" the Copyright notice even if
> this file doesn't contain new things.  After all, if you moved things
> around, they were already covered by the copyright of the file which
> they belonged before.


But then if you follow that patch one extra step, you can rename
the files back to their original names, and what you end up with
is exactly with you started with, except you've lost all your copyright
years.  If that's okay, then I've just proven that a copyright year list
is insignificant and unnecessary, and we can just go do a wholesale pass
on the whole codebase replacing all the multiple years by a single
"2012" year.

> Anyway, I'm not an expert, so thanks for clarifying.


I'm not an expert either.  Better ask the FSF indeed.  But please do
raise my point above with them.

-- 
Pedro Alves


  reply	other threads:[~2012-04-18  9:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-15 20:27 Doug Evans
2012-04-16  7:27 ` Sergio Durigan Junior
2012-04-16 10:52   ` Pedro Alves
2012-04-16 19:11     ` Sergio Durigan Junior
2012-04-18  9:43       ` Pedro Alves [this message]
2012-04-19 17:37         ` Sergio Durigan Junior
2012-04-20 15:09           ` Pedro Alves
2012-04-16 20:06     ` Tom Tromey
2012-04-16 20:42       ` Pedro Alves
2012-04-16 20:59         ` Tom Tromey
2012-04-17 22:41           ` Doug Evans
2012-04-16 20:10   ` Tom Tromey
2012-04-17 22:54   ` Doug Evans
2012-04-17 22:59     ` Joel Brobecker
2012-04-18  4:26       ` Sergio Durigan Junior
2012-04-18  6:22         ` Joel Brobecker
2012-04-16 10:40 ` Pedro Alves
2012-04-18 14:02 ` Yao Qi
2012-04-18 14:32   ` Tom Tromey
2012-04-16  2:07 Doug Evans

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=4F8E8A37.6070900@redhat.com \
    --to=palves@redhat.com \
    --cc=dje@sebabeach.org \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@redhat.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