unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: storm@cua.dk, emacs-devel@gnu.org
Subject: Re: Installing patches without getting legal papers.
Date: Wed, 30 Oct 2002 12:16:50 -0500	[thread overview]
Message-ID: <E186wSY-0002pQ-00@fencepost.gnu.org> (raw)
In-Reply-To: <20021029083512.A082.LEKTU@terra.es> (message from Juanma Barranquero on Tue, 29 Oct 2002 08:37:22 +0100)

The purpose of "(tiny change)" is to help us keep track of the changes
for which we did not need legal papers.

    Just a question: how many lines of change are considered "tiny"?

A tiny change is one so small we don't need legal papers for it.
See maintain.texi for the criterion for that.

    ! 2002-10-16  Luc Teirlinck  <teirllm@mail.auburn.edu>  (tiny change)

We have papers from Luc, so it is not useful to put "(tiny change)"
on his changes.  Big or small, they are all covered by papers.

Please only use "(tiny change)" in the cases where we install
a change from someone who did not give us legal papers.

However, it's the total size of that person's changes that determines
whether we need papers.  So each time you install such a change,
always search for the person's name to see if there are other changes
(in C or in Lisp) by the same person.  If there are other changes,
please look at the total size of the new change and the old ones.  If
the total is big enough to need papers, then don't install the new
change.

  reply	other threads:[~2002-10-30 17:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-28 22:44 Installing patches without getting legal papers Kim F. Storm
2002-10-29  7:37 ` Juanma Barranquero
2002-10-30 17:16   ` Richard Stallman [this message]
2002-10-30 17:48     ` Juanma Barranquero
2002-10-31 17:26       ` Richard Stallman
2002-11-04  7:40     ` Juanma Barranquero
2002-11-04 18:06       ` Richard Stallman
2002-10-29 11:29 ` Richard Stallman
2002-10-29 17:19 ` Francesco Potorti`
2002-10-30 17:18   ` Richard Stallman

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E186wSY-0002pQ-00@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=storm@cua.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).