From: Michael Chastain <mec.gnu@mindspring.com>
To: rsandifo@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [committed] Regenerate sim/frv from cpu/frv.cpu
Date: Fri, 27 Aug 2004 11:06:00 -0000 [thread overview]
Message-ID: <412F15BB.nailK1Z1V9NHP@mindspring.com> (raw)
In-Reply-To: <87hdqooqqw.fsf@redhat.com>
> -Copyright 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003 Free Software Foundation, Inc.
> +Copyright 1996-2004 Free Software Foundation, Inc.
Hi Richard,
The Gnu standard for copyright notices is to spell out each year
without using ranges:
Copyright 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004
Free Software Foundation, Inc.
This is from:
http://www.gnu.org/prep/maintain_8.html#SEC8
Think of the copyright notice as a statement in a very picky
language that is interpreted by a very hostile interpreter.
next prev parent reply other threads:[~2004-08-27 11:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 9:49 Richard Sandiford
2004-08-27 11:06 ` Michael Chastain [this message]
2004-08-27 12:34 ` Richard Sandiford
2004-08-27 15:53 ` Dave Brolley
2004-08-27 20:18 ` Frank Ch. Eigler
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=412F15BB.nailK1Z1V9NHP@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=gdb-patches@sources.redhat.com \
--cc=rsandifo@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