From: Joel Brobecker <brobecker@adacore.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: FYI: copyright years updated...
Date: Sun, 06 Jan 2013 13:59:00 -0000 [thread overview]
Message-ID: <20130106135856.GD3703@adacore.com> (raw)
In-Reply-To: <20130106133106.GD30067@redhat.com>
> How come people are committing copyright year-2013 updates at the
> *beginning* of the year - before any changes have been made?
I am not a lawyer, and just follow the recommendation from the FSF
as I understand it (documented in "Information for Maintainers
of GNU Software). I don't know if the update needs to wait for
a significant change, or not, or whether the copyright update it itself
is a legally significant change. Regardless, I was pretty sure that
pending another end of the world, someone was going to make a significant
change sometime in 2013... Just the ChangeLog rotation, for instance,
which was made prior to the copyright update, could qualify as
a significant change...
--
Joel
prev parent reply other threads:[~2013-01-06 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-01 6:51 Joel Brobecker
2013-01-04 16:05 ` Frank Ch. Eigler
2013-01-06 6:54 ` Joel Brobecker
2013-01-06 13:31 ` Frank Ch. Eigler
2013-01-06 13:59 ` Joel Brobecker [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=20130106135856.GD3703@adacore.com \
--to=brobecker@adacore.com \
--cc=fche@redhat.com \
--cc=gdb-patches@sourceware.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