From: Richard Stallman <rms@gnu.org>
To: Yuan Fu <casouri@gmail.com>
Cc: larsi@gnus.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: How to distribute dynamic modules by themselves?
Date: Sun, 27 Mar 2022 01:27:43 -0400 [thread overview]
Message-ID: <E1nYLRH-0008CJ-U6@fencepost.gnu.org> (raw)
In-Reply-To: <1CD02B14-06CC-4D8F-8CC0-A9C214FA2AED@gmail.com> (message from Yuan Fu on Thu, 24 Mar 2022 22:53:33 -0700)
[[[ 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. ]]]
> > Github is a bad choice, for moral reasons -- see
> > https://www.gnu.org/software/repo-criteria-evaluation.html for
> > explanation of why. How about choosing a better repo?
> I’m aware of GitHub’s issues, but…
But what? If you spell out what you're concerned about we
may find a workaround.
You can reply off the list.
--
Dr Richard Stallman (https://stallman.org)
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:[~2022-03-27 5:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 23:51 How to distribute dynamic modules by themselves? Yuan Fu
2022-03-21 1:31 ` Zhu Zihao
2022-03-22 5:07 ` Richard Stallman
2022-03-22 8:44 ` Zhu Zihao
2022-03-23 3:55 ` Richard Stallman
2022-03-23 19:44 ` Yuan Fu
2022-03-25 3:29 ` Richard Stallman
2022-03-23 11:20 ` Lars Ingebrigtsen
2022-03-23 19:48 ` Yuan Fu
2022-03-25 3:29 ` Richard Stallman
2022-03-25 5:53 ` Yuan Fu
2022-03-27 5:27 ` Richard Stallman
2022-03-27 5:27 ` Richard Stallman [this message]
2022-03-23 22:16 ` Stefan Monnier
2022-03-23 22:30 ` Ergus
2022-03-24 3:19 ` 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=E1nYLRH-0008CJ-U6@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=casouri@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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.