From: "Frank Ch. Eigler" <fche@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/copyright] lib/java.exp: update copyright years
Date: Wed, 21 Jul 2004 11:53:00 -0000 [thread overview]
Message-ID: <20040721115337.GG10977@redhat.com> (raw)
In-Reply-To: <9003-Wed21Jul2004061952+0300-eliz@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
Hi -
On Wed, Jul 21, 2004 at 06:19:52AM +0200, Eli Zaretskii wrote:
> [...]
> I'd suggest to think again. As paranoiac as this looks at first
> glance, if the Linux kernel developers did something remotely
> paranoiac since day one, they wouldn't be facing the ridiculous SCO/MS
> lawsuits these days.
I know you're being serious, but this seems to lack all sense of
proportion. If you want to tag an FSF copyright on every little scrap of
text, go right ahead. But why do experienced technical people believe
that adding or modifying comments like this, or reindenting a piece of
a file, should reasonably require all this mass of communication and
formality and process? It doesn't make the work somehow more significant
in the grand scheme of things, only more tedious to filter out.
> They seem to understand this now (contributors are nowadays required
> to sign papers), [...]
I believe you misunderstand the new proposed process.
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-07-21 11:53 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
2004-07-21 3:21 ` Eli Zaretskii
2004-07-21 11:53 ` Frank Ch. Eigler [this message]
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=20040721115337.GG10977@redhat.com \
--to=fche@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@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