From: Richard Stallman <rms@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: jay.p.belanger@gmail.com, emacs-devel@gnu.org
Subject: Re: Submission of Matrix Kronecker Product for calc
Date: Sat, 08 Mar 2008 01:29:05 -0500 [thread overview]
Message-ID: <E1JXsYL-0003hZ-O9@fencepost.gnu.org> (raw)
In-Reply-To: <yg3ar2icqs.fsf@fencepost.gnu.org> (message from Glenn Morris on Fri, 07 Mar 2008 13:56:59 -0500)
Isn't there something to be said for: i) assuming that contributors
will want to continue contributing; and ii) trying to minimize the
number of pieces of paper people have to sign?
If someone thinks he may want to contribute more
then he might prefer to sign the future assignment.
The form for disclaimers mentions this option.
I've always offered
assign-past-and-future for the whole of Emacs as a default option to
contributors, no matter how much they contribute initially. Should I
stop doing this? Is there some reason to actually _prefer_ a
disclaimer for smaller changes?
The disclaimer is not better for us, but it is smaller and simpler so
some contributors may prefer it. That seems like a reason to suggest
both options, in the case of a medium contribution from someone who
may not want to contribute more. request-disclaim.changes does that.
next prev parent reply other threads:[~2008-03-08 6:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 12:43 Submission of Matrix Kronecker Product for calc Vincent Belaïche
2008-03-05 21:00 ` Jay Belanger
2008-03-05 22:09 ` David Kastrup
2008-03-06 1:25 ` Jay Belanger
2008-03-06 8:36 ` David Kastrup
2008-03-07 3:36 ` Richard Stallman
2008-03-07 3:38 ` Richard Stallman
2008-03-07 18:56 ` Glenn Morris
2008-03-08 6:29 ` Richard Stallman [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-03-02 21:37 Vincent Belaïche
2008-03-05 3:22 ` Jay Belanger
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=E1JXsYL-0003hZ-O9@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jay.p.belanger@gmail.com \
--cc=rgm@gnu.org \
/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).