From: Michael Chastain <mec.gnu@mindspring.com>
To: eliz@gnu.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/testsuite] ChangeLog: add copyright notice
Date: Tue, 10 Aug 2004 19:38:00 -0000 [thread overview]
Message-ID: <41192439.nailAIZ1AOBGD@mindspring.com> (raw)
In-Reply-To: <9003-Tue10Aug2004215449+0300-eliz@gnu.org>
Okay, I committed this patch.
eliz> This principle is okay for patching code, but for such small changes
eliz> in something other than code, I think sticking to it is overkill.
When it comes to copyright, I'm pretty sticky about principles.
Also there is not much difference between "code" and "other than code"
for copyright purposes.
eliz> Attached below.
Cool, I will review your patch in a few minutes.
Michael C
2004-08-07 Michael Chastain <mec.gnu@mindspring.com>
* ChangeLog: Add copyright notice. The notice is copied
from emacs 21.3 top level ChangeLog.
next prev parent reply other threads:[~2004-08-10 19:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-06 16:26 Michael Chastain
2004-08-07 16:07 ` Eli Zaretskii
2004-08-07 23:06 ` Michael Chastain
2004-08-10 18:57 ` Eli Zaretskii
2004-08-10 19:38 ` Michael Chastain [this message]
2004-08-10 19:39 ` Michael Chastain
2004-08-11 3:58 ` Eli Zaretskii
2004-08-11 7:46 ` Michael Chastain
2004-08-14 13:23 ` 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=41192439.nailAIZ1AOBGD@mindspring.com \
--to=mec.gnu@mindspring.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