From: Richard Stallman <rms@gnu.org>
To: tumashu <tumashu@163.com>
Cc: emacs-devel@gnu.org
Subject: Re: How to deal with GPL paper when the contributer can not contact with?
Date: Sat, 26 Sep 2020 00:32:21 -0400 [thread overview]
Message-ID: <E1kM1sj-0002jw-Tb@fencepost.gnu.org> (raw)
In-Reply-To: <2ad5cc9d.114d.174c2e75e20.Coremail.tumashu@163.com> (message from tumashu on Fri, 25 Sep 2020 09:36:16 +0800 (CST))
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> 2. his patchs are rewrite ivy.el and swiper.el's exist functions,
> so many code of his patch come from ivy.el and swiper.el, ivy.el
> and swiper.el are gnu-elpa packages.
> How should I do? wait or elimit his commit?
How many of those lines contain code he wrote?
There is no need to count the code that he left unchanged.
If what he wrote is short, and not crucial, then you can ignore
the copyright issue for that.
Or you can rewrite the code some other way. It sounds like that
won't be a lot of work.
--
Dr Richard Stallman
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2020-09-26 4:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 1:36 How to deal with GPL paper when the contributer can not contact with? tumashu
2020-09-25 2:40 ` Stefan Monnier
2020-09-25 4:07 ` tumashu
2020-09-26 4:32 ` Richard Stallman [this message]
2020-09-26 7:12 ` tumashu
2020-09-27 2:45 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1kM1sj-0002jw-Tb@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=tumashu@163.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.