From: Jai Flack <jflack@posteo.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>, 54662@debbugs.gnu.org
Subject: bug#54662: 29.0.50; [PATCH] An mu backend for gnus-search
Date: Sun, 03 Apr 2022 02:26:55 +0000 [thread overview]
Message-ID: <871qyesxzk.fsf@posteo.net> (raw)
In-Reply-To: <87mth3ik0i.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 02 Apr 2022 17:26:37 +0200")
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> This was one of the questions in the original emacs.devel thread -- how
>> do we handle the situation where a package is both built-in and
>> available for installation from ELPA? Does anything special need to
>> happen in order to make sure the user is always using the newest
>> version?
>
> I'd rather have it all in-core if things are tightly coupled.
My only reason for the ELPA package was to make this available for users
of Emacs 28 (once it's released). If you don't think this is necessary
then I have no reason for the savannah project.
- --
Thanks,
Jai
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEMibxCPhhYAWzlyCbGp8lHZSJ3Z4FAmJJBfQACgkQGp8lHZSJ
3Z6U4w/9FQvR0R605JpQc9+VZ090dPSeATk8vV0dxC4l3CNRxfM2MY/BHN+7OF/5
+QCe+oZFvDWvGv5sPCh/cbwtiG7+pqOiPvtShF+bPT8oFtDLnRJZAlfOpsgTC8AB
rjoYmegBQ82BZOMtNxAPh4PxVcIJC6PQTq/BvMIxtrNY9Kngz/FIpk9LM2GD24M3
eK493vb088jdNikXeIvqqmt7GpT9bLJM62VlQDmPkZ7C2+OGx9ZeuDGWiS4OFMV5
DTQrj5o8zye2YEhp1mx1werO3oaUr9EOLRSJJ6OEsxlrpACyKQffCag8XRhikOJi
z2aOpVpKGSkePR1Eij9gnk9X6Ov9ZwFW3o/I9FhtqBYFNqS35liz/mJwZDTNYJpP
Hpd1Lck2zTR7wJsYiO7IEACmOx8WMSGDDS6Sc0vs4E3RyFOrZbeie2n7k25Nl5r9
E7FO37IOif4/lxKAMm0wWyHYteRZKotj/HcW5nY8DHivK2b65kQgpFXmEzLt1iqT
PvlWn4k1c+JrhvN/tyKxKFdRz3GUpRDADKdDyX1W81kvtNZuUFhRjdpUmolrA7nB
S3lJWnQwxSQwtrf3qtVRRgcT5WuUDsYELWWWEhLGHXKW7H6rX9JTaejW+34XJcRM
0aq9jtetjDjfpLkkIcFdZdzCrt53pkBzIq4xZlQeerpi8n+ziyk=
=e2Fg
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2022-04-03 2:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 1:39 bug#54662: 29.0.50; [PATCH] An mu backend for gnus-search Jai Flack via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-02 14:58 ` Lars Ingebrigtsen
2022-04-02 15:13 ` Corwin Brust
2022-04-02 15:25 ` Eric Abrahamsen
2022-04-02 15:28 ` Corwin Brust
2022-04-02 16:12 ` Eric Abrahamsen
2022-04-02 16:14 ` Corwin Brust
2022-04-03 2:28 ` Jai Flack
2022-04-02 15:21 ` Eric Abrahamsen
2022-04-02 15:26 ` Lars Ingebrigtsen
2022-04-03 2:26 ` Jai Flack [this message]
2022-04-03 12:00 ` Lars Ingebrigtsen
2022-04-03 14:53 ` Jai Flack
2022-04-04 10:30 ` Lars Ingebrigtsen
2022-04-04 12:29 ` Jai Flack
2022-04-06 9:15 ` Lars Ingebrigtsen
2022-04-06 23:31 ` Jai Flack
2022-04-07 11:14 ` Lars Ingebrigtsen
2022-04-07 11:26 ` Jai Flack
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=871qyesxzk.fsf@posteo.net \
--to=jflack@posteo.net \
--cc=54662@debbugs.gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=larsi@gnus.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).