From: Joel Brobecker <brobecker@adacore.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Add support for the Renesas rl78 architecture
Date: Fri, 27 Jan 2012 05:48:00 -0000 [thread overview]
Message-ID: <20120127053431.GX31383@adacore.com> (raw)
In-Reply-To: <20120126170214.3a99b42f@mesquite.lan>
> With regard to copyright years, I made sure that each new file lists
> both 2011 and 2012. As stated earlier, versions of these files were
> released to our customer in 2011.
You could ask the FSF (email copyright-cleark - using fsf dot org
as the domain), and the answer would be interesting to everyone.
It would give us a better understanding of what the important factor
is. Is it the time of first writing, time of first release (define
release). Making changes seem to be the important factor, at least
as far as adding copyright years is concerned.
For now, I would leave 2011. I think it's been the current practice
(certainly, it's been mine). I don't know how important it is, but
it affects when older versions might theoretically go into the public
domain.
--
Joel
next prev parent reply other threads:[~2012-01-27 5:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 1:21 Kevin Buettner
2012-01-26 2:24 ` Mike Frysinger
2012-01-26 9:18 ` Pedro Alves
2012-01-26 16:59 ` Kevin Buettner
2012-01-26 19:16 ` Mike Frysinger
2012-01-26 6:21 ` Joel Brobecker
2012-01-26 21:50 ` Sergio Durigan Junior
2012-01-26 23:24 ` Kevin Buettner
2012-01-27 0:23 ` Kevin Buettner
2012-01-27 2:02 ` Mike Frysinger
2012-01-27 5:48 ` Joel Brobecker [this message]
2012-01-30 22:44 ` Kevin Buettner
2012-01-30 3:11 ` Yao Qi
2012-01-30 23:05 ` Kevin Buettner
2012-01-30 23:58 ` Kevin Buettner
2012-02-04 6:06 ` Kevin Buettner
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=20120127053431.GX31383@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@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