From: "Jim Blandy" <jimb@red-bean.com>
To: "Jim Blandy" <jimb@red-bean.com>,
"Gaius Mulley" <gaius@glam.ac.uk>,
gdb-patches@sources.redhat.com
Subject: Re: Enhanced language support for Modula-2
Date: Mon, 20 Feb 2006 21:42:00 -0000 [thread overview]
Message-ID: <8f2776cb0602201322o3791841dv2916e53181e9f308@mail.gmail.com> (raw)
In-Reply-To: <20060220150513.GB14155@nevyn.them.org>
On 2/20/06, Daniel Jacobowitz <drow@false.org> wrote:
> Do you think we need copyright paperwork for Waldek's patch? I think
> it's sufficiently trivial.
Below is what I'm going by, from the Project GNU's 'maintain.texi'.
It meets the size requirement, and while much of the patch is
repetitions of similar patterns nearby, read_set_type isn't a direct
tweake copy of anything. I think it's borderline, which to me means
we need paperwork.
@node Legally Significant
@section Legally Significant Changes
If a person contributes more than around 15 lines of code and/or text
that is legally significant for copyright purposes, which means we
need copyright papers for it as described above.
A change of just a few lines (less than 15 or so) is not legally
significant for copyright. A regular series of repeated changes, such
as renaming a symbol, is not legally significant even if the symbol
has to be renamed in many places. Keep in mind, however, that a
series of minor changes by the same person can add up to a significant
contribution. What counts is the total contribution of the person; it
is irrelevant which parts of it were contributed when.
next prev parent reply other threads:[~2006-02-20 21:22 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 23:15 Gaius Mulley
2006-02-16 0:20 ` Jim Blandy
2006-02-16 11:06 ` Gaius Mulley
2006-02-20 15:05 ` Daniel Jacobowitz
2006-02-20 21:42 ` Jim Blandy [this message]
2006-02-21 11:06 ` Gaius Mulley
2006-02-21 19:01 ` Jim Blandy
2006-02-25 13:17 ` Gaius Mulley
2006-02-26 5:44 ` Jim Blandy
2006-02-26 5:46 ` Daniel Jacobowitz
2006-02-28 5:37 ` Gaius Mulley
2006-02-28 13:53 ` Jim Blandy
2006-03-02 8:57 ` Gaius Mulley
2006-03-02 17:27 ` Jim Blandy
2006-02-21 19:21 ` Jim Blandy
2006-02-21 20:51 ` Eli Zaretskii
2006-02-21 20:50 ` Eli Zaretskii
2006-02-21 20:57 ` Mark Kettenis
2006-02-22 5:33 ` Eli Zaretskii
2006-02-22 18:36 ` Eli Zaretskii
2006-02-16 4:34 ` Eli Zaretskii
2006-02-16 11:11 ` Gaius Mulley
2006-04-20 13:23 Gaius Mulley
2006-04-20 14:35 ` Eli Zaretskii
2006-04-20 18:47 ` Mark Kettenis
2006-04-20 18:54 ` Eli Zaretskii
2006-05-04 7:17 ` Gaius Mulley
2006-05-04 15:37 ` Daniel Jacobowitz
2006-05-04 18:01 ` Jim Blandy
2006-05-08 14:09 ` Gaius Mulley
2006-05-08 17:47 ` Jim Blandy
2006-05-09 22:57 ` Gaius Mulley
2006-05-10 21:45 ` Jim Blandy
2006-05-11 12:37 ` Gaius Mulley
2006-05-12 18:18 ` Joel Brobecker
2006-05-12 18:27 ` Jim Blandy
2006-05-13 13:31 ` Gaius Mulley
2006-05-13 11:02 ` Gaius Mulley
2006-05-08 21:03 ` Eli Zaretskii
2006-05-04 16:12 ` 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=8f2776cb0602201322o3791841dv2916e53181e9f308@mail.gmail.com \
--to=jimb@red-bean.com \
--cc=gaius@glam.ac.uk \
--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