From: "Eli Zaretskii" <eliz@gnu.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/copyright] lib/java.exp: update copyright years
Date: Wed, 21 Jul 2004 18:22:00 -0000 [thread overview]
Message-ID: <2914-Wed21Jul2004212050+0300-eliz@gnu.org> (raw)
In-Reply-To: <20040721115337.GG10977@redhat.com> (fche@redhat.com)
> Date: Wed, 21 Jul 2004 07:53:37 -0400
> From: "Frank Ch. Eigler" <fche@redhat.com>
>
> I know you're being serious
Dead serious.
> 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?
Because people involved want to understand the issues, and I
personally find that a very reasonable attitude.
> > They seem to understand this now (contributors are nowadays required
> > to sign papers), [...]
>
> I believe you misunderstand the new proposed process.
Then perhaps we will see more lawsuits in the future.
next prev parent reply other threads:[~2004-07-21 18: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
2004-07-21 3:21 ` Eli Zaretskii
2004-07-21 11:53 ` Frank Ch. Eigler
2004-07-21 18:22 ` Eli Zaretskii [this message]
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=2914-Wed21Jul2004212050+0300-eliz@gnu.org \
--to=eliz@gnu.org \
--cc=fche@redhat.com \
--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