From: "Ludovic Courtès" <ludo@gnu.org>
To: Xinglu Chen <public@yoctocell.xyz>
Cc: Liliana Marie Prikler <liliana.prikler@gmail.com>,
52774-done@debbugs.gnu.org
Subject: bug#52774: [PATCH] import: elpa: Also check NonGNU ELPA for updates.
Date: Wed, 05 Jan 2022 23:18:06 +0100 [thread overview]
Message-ID: <875yqxj081.fsf_-_@gnu.org> (raw)
In-Reply-To: <87ee5zbknh.fsf@yoctocell.xyz> (Xinglu Chen's message of "Sun, 26 Dec 2021 13:44:34 +0100")
Hi,
Xinglu Chen <public@yoctocell.xyz> skribis:
> From 4332502000bd06a2be900c236666d10f07777807 Mon Sep 17 00:00:00 2001
> Message-Id: <4332502000bd06a2be900c236666d10f07777807.1640522590.git.public@yoctocell.xyz>
> From: Xinglu Chen <public@yoctocell.xyz>
> Date: Thu, 23 Dec 2021 22:08:33 +0100
> Subject: [PATCH] import: elpa: Also check NonGNU ELPA for updates.
>
> * elpa.scm (latest-release): Determine the repository based on the URL of the
> source.
> (package-from-gnu.org?): Rename to ...
> (elpa-repository): ...this; memoize.
> (elpa-package?): New procedure.
> (%elpa-updater): Adjust accordingly.
Applied, thanks to the two of you!
I had to rename ‘elpa-package?’ because:
guix/import/elpa.scm:459:0: warning: shadows previous definition of `elpa-package?' at <unknown-location>
(The other ‘elpa-package?’ predicate wasn’t used, but still.)
Ludo’.
next prev parent reply other threads:[~2022-01-05 22:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-24 11:25 [bug#52774] [PATCH] import: elpa: Also check NonGNU ELPA for updates Xinglu Chen
2021-12-24 12:17 ` Liliana Marie Prikler
2021-12-25 9:44 ` Xinglu Chen
2021-12-25 10:15 ` Liliana Marie Prikler
2021-12-25 14:31 ` Xinglu Chen
2021-12-25 15:23 ` Liliana Marie Prikler
2021-12-26 12:44 ` Xinglu Chen
2021-12-26 13:08 ` Liliana Marie Prikler
2022-01-05 22:18 ` Ludovic Courtès [this message]
2022-01-05 23:03 ` Liliana Marie Prikler
2022-01-05 23:12 ` Liliana Marie Prikler
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=875yqxj081.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=52774-done@debbugs.gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=public@yoctocell.xyz \
/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/guix.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.