From: muller@cerbere.u-strasbg.fr
To: Eli Zaretskii <eliz@is.elta.co.il>, muller@cerbere.u-strasbg.fr
Cc: gdb@sources.redhat.com
Subject: Re: [RFA] Correct machine name in config/m68k/tm-nbsd.h
Date: Thu, 25 Apr 2002 15:19:00 -0000 [thread overview]
Message-ID: <3.0.6.32.20020426002406.01062100@ics.u-strasbg.fr> (raw)
In-Reply-To: <2593-Thu25Apr2002211843+0300-eliz@is.elta.co.il>
At 21:18 25/04/02 +0300, Eli Zaretskii wrote:
>> Date: Thu, 25 Apr 2002 12:42:42 +0200
>> From: Pierre Muller <muller@cerbere.u-strasbg.fr>
>> >
>> >FYI, the guidelines for such decisions are in standards.texi (IIRC).
>> Sorry, but I went trough (quickly)
>> but didn't find anything about
>> years for copyrights.
>
>Sorry, my memory betrayed me: the guidelines I had in mind are in
>maintain.texi, not in standards.texi. (You can download maintain.texi
>from the GNU FTP site, if you don't have it.) Look for a node
>"Copyright Notices" in that manual.
Extracted from this file:
<<<<<<<<<<<<<<<<<<<<<
The list of year numbers should include each year in which you finished
preparing a version which was actually released, and which was an
ancestor of the current version.
Please reread the paragraph above, slowly and carefully. It is
important to understand that rule precisely, much as you would
understand a complicated C statement in order to hand-simulate it.
This list is _not_ a list of years in which versions were _released_.
It is a list of years in which versions, later released, were
_completed_. So if you finish a version on Dec 31, 1994 and release it
on Jan 1, 1995, this version requires the inclusion of 1994, but
doesn't require the inclusion of 1995.
<<<<<<<<<<<<<<<<<<<<<
After rereading, I understand that we should only add a year number
each time we release a version we should update the copyright
notice with the year corresponding to the last commit before
the release....
Shouldn't this be done automatically by some script??
Anyhow, as I understand this, I will not add 2002 to the year list,
as it might well be that we only release GDB 6.0 next year,
so if we add some other change in early 2003, that 2002
should not be in the list according to that rule!
But maybe I didn't reread it slowly enough....
next prev parent reply other threads:[~2002-04-25 22:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020424102300.B6310@nevyn.them.org>
[not found] ` <4.2.0.58.20020425123916.016f4370@ics.u-strasbg.fr>
2002-04-25 11:19 ` Eli Zaretskii
2002-04-25 15:19 ` muller [this message]
2002-04-25 16:07 ` Daniel Jacobowitz
2002-04-28 9:52 ` Eli Zaretskii
2002-04-28 10:00 ` Daniel Jacobowitz
2002-04-28 11:50 ` Eli Zaretskii
2002-04-29 8:26 ` Daniel Jacobowitz
2002-04-29 11:39 ` Eli Zaretskii
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=3.0.6.32.20020426002406.01062100@ics.u-strasbg.fr \
--to=muller@cerbere.u-strasbg.fr \
--cc=eliz@is.elta.co.il \
--cc=gdb@sources.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