unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Eshel Yaron <me@eshelyaron.com>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org,
	jan@swi-prolog.org, james.cash@occasionallycogent.com
Subject: Re: [NonGNU ELPA] New package: sweep
Date: Thu, 29 Sep 2022 22:36:23 -0400	[thread overview]
Message-ID: <E1oe5t1-0000eF-H0@fencepost.gnu.org> (raw)
In-Reply-To: <m1bkr0etfg.fsf@esmac.lan> (message from Eshel Yaron on Tue, 27 Sep 2022 18:19:31 +0300)

[[[ 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. ]]]

  > Thanks for looking into it.  Its true that I've authored most of this
  > package up to this point, but this project is still in its early days
  > and I hope that going forward it will receive contributions from the
  > (SWI-)Prolog community (including more help from James :) as you noted).

If the package is a success, it surely will get contributions from
some of them.

But I don't follow the rest -- it seems to skip over something:

  > For that reason I would prefer to target NonGNU ELPA, at least for the
  > time being.  

I don't see any reason for that preference.  Perhaps you left out a
crucial link between the two parts.





-- 
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)





  reply	other threads:[~2022-09-30  2:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-26 10:22 [NonGNU ELPA] New package: sweep Eshel Yaron
2022-09-26 17:41 ` Stefan Monnier
2022-09-27 15:19   ` Eshel Yaron
2022-09-30  2:36     ` Richard Stallman [this message]
2022-09-27 16:17 ` Richard Stallman
2022-09-27 18:47   ` Juri Linkov
2022-09-28  5:40     ` Andrea G. Monaco
2022-09-30  2:36     ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2022-09-26 11:29 Eshel Yaron
2022-09-26 19:32 ` Philip Kaludercic
2022-09-27 16:32   ` Eshel Yaron
2022-09-27 17:46     ` Philip Kaludercic
2022-09-28  6:46       ` Eshel Yaron
2022-09-28  7:27         ` Philip Kaludercic
2022-09-28 17:49           ` Juri Linkov
2022-09-28 18:41             ` Eli Zaretskii
2022-09-28 18:56             ` Philip Kaludercic
2022-09-30  2:38             ` Richard Stallman
2022-09-30  8:20             ` Stefan Kangas
2022-09-30  9:45               ` Robert Pluim
2022-09-29  2:59         ` Richard Stallman
2022-09-27 18:49     ` Stefan Monnier
2022-09-28  7:15       ` Eshel Yaron
2022-09-29  3:02     ` Richard Stallman
2022-09-29  5:04       ` Eshel Yaron
2022-09-29  6:17       ` Eli Zaretskii

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=E1oe5t1-0000eF-H0@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=james.cash@occasionallycogent.com \
    --cc=jan@swi-prolog.org \
    --cc=me@eshelyaron.com \
    --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 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).