From: Richard Stallman <rms@gnu.org>
Cc: monnier+gnu/emacs@rum.cs.yale.edu
Subject: Re: Incorporating patches into GNU Emacs
Date: Sat, 19 Apr 2003 09:35:47 -0400 [thread overview]
Message-ID: <E196sVP-0004r1-00@fencepost.gnu.org> (raw)
In-Reply-To: <200304190314.h3J3EcUY016384@gbr.newt.com> (message from Bill Wohler on Fri, 18 Apr 2003 20:14:38 -0700)
That's what I thought. At which point do the changes become nontrivial?
We can use up to 10 to 20 lines from one person before we
need papers.
next prev parent reply other threads:[~2003-04-19 13:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-19 3:14 Incorporating patches into GNU Emacs Bill Wohler
2003-04-19 13:35 ` Richard Stallman [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-18 16:11 Bill Wohler
2003-04-18 17:42 ` Stefan Monnier
2003-04-19 0:47 ` Kim F. Storm
2003-04-18 6:40 Bill Wohler
2003-04-18 8:27 ` Steve Youngs
2003-04-19 4:14 ` Richard Stallman
2003-04-18 3:31 Bill Wohler
2003-04-18 5:29 ` Steve Youngs
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=E196sVP-0004r1-00@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=monnier+gnu/emacs@rum.cs.yale.edu \
/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).