From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Michael Snyder <msnyder@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Update copyright dates in gdb.texinfo
Date: Fri, 31 Mar 2006 19:47:00 -0000 [thread overview]
Message-ID: <20060331135551.GA27463@nevyn.them.org> (raw)
In-Reply-To: <u3bgzavsi.fsf@gnu.org>
On Fri, Mar 31, 2006 at 11:00:13AM +0300, Eli Zaretskii wrote:
> > Date: Thu, 30 Mar 2006 18:05:28 -0800
> > From: Michael Snyder <msnyder@redhat.com>
> >
> > Ok Eli?
>
> Yes, thanks. But I thought we all agreed that copyright years need to
> be changed only as part of preparing a release, and that at that time
> all files need to be stamped with the release year. Did I miss
> something?
Isn't it the other way around? We can gratuitously bump the copyright
year on files, and the FSF even recommends it, but CVS counts as "a
release" for the FSF's copyright purposes.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-03-31 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-31 8:03 Michael Snyder
2006-03-31 10:40 ` Eli Zaretskii
2006-03-31 19:47 ` Daniel Jacobowitz [this message]
2006-03-31 22:17 ` Eli Zaretskii
2006-03-31 22:19 ` Michael Snyder
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=20060331135551.GA27463@nevyn.them.org \
--to=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@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