From: fche@redhat.com (Frank Ch. Eigler)
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/copyright] lib/java.exp: update copyright years
Date: Tue, 20 Jul 2004 21:22:00 -0000 [thread overview]
Message-ID: <y0misciz85h.fsf@toenail.toronto.redhat.com> (raw)
In-Reply-To: <20040719213256.177364B104@berman.michael-chastain.com>
mec.gnu@mindspring.com (Michael Elizabeth Chastain) writes:
> This patch adds the copyright year 2004 to java.exp.
> The file was modified this year.
> Tested on native i686-pc-linux-gnu.
> [...]
> * lib/java.exp: Update copyright notice.
> [...]
I am surprised to see how much effort is being expended on this, and
how tiringly verbose it is. This is like putting a long-winded
ChangeLog message together for every spelling correction in a comment,
then posting the patch, then discussing it for a while to debate
English versus American spellings. Process rigidity run amok!
- FChE
next prev parent reply other threads:[~2004-07-20 21:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-19 21:32 Michael Elizabeth Chastain
2004-07-20 21:22 ` Frank Ch. Eigler [this message]
2004-07-21 3:21 ` Eli Zaretskii
2004-07-21 11:53 ` Frank Ch. Eigler
2004-07-21 18:22 ` Eli Zaretskii
2004-07-21 19:54 ` 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=y0misciz85h.fsf@toenail.toronto.redhat.com \
--to=fche@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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