From: Ryan Prior <rprior@protonmail.com>
To: John Soo <jsoo1@asu.edu>
Cc: guix-devel@gnu.org, "Ludovic Courtès" <ludo@gnu.org>,
"Giovanni Biscuolo" <g@xelera.eu>,
"GNU Guix maintainers" <guix-maintainers@gnu.org>
Subject: Re: emacs-guix (upstream) needs more love: a survey of repositories, homepage and issues
Date: Wed, 27 Apr 2022 15:31:31 +0000 [thread overview]
Message-ID: <pnU7824Wd9EPFc7dPtHHD0mWRtKEVnNXYgk42hy1f3dJGptV7ToSv7cyF9j2toTLn853jMQAuofOR_u5NDS5hVpC99cEaNfIa60FpT6GyH0=@protonmail.com> (raw)
In-Reply-To: <e80503a5-340c-470d-a972-7a0804be8494@Canary>
[-- Attachment #1: Type: text/plain, Size: 452 bytes --]
On Wednesday, April 27th, 2022 at 2:01 PM, John Soo <jsoo1@asu.edu> wrote:
> Hi Gio!
>
> I am very sorry I have let it slip.
No worries! I am planning this weekend to try out the fixes in 55013 (and try building from upstream savannah; I didn't realize that was different from what we have in guix) and this weekend to see if we can get something working "out of the box."
We appreciate your work on getting emacs-guix back into shape!
Cheers,
Ryan
[-- Attachment #2: Type: text/html, Size: 920 bytes --]
next prev parent reply other threads:[~2022-04-27 15:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 13:16 emacs-guix (upstream) needs more love: a survey of repositories, homepage and issues Giovanni Biscuolo
2022-04-27 14:01 ` John Soo
2022-04-27 15:31 ` Ryan Prior [this message]
2022-04-28 16:31 ` Giovanni Biscuolo
2022-04-28 8:08 ` Ludovic Courtès
2022-04-28 16:27 ` Giovanni Biscuolo
2022-04-29 10:12 ` zimoun
2022-05-23 14:39 ` Ludovic Courtès
2022-05-23 15:36 ` Kaelyn
2022-05-26 15:01 ` Giovanni Biscuolo
2022-05-26 23:15 ` Kaelyn
2022-05-27 6:32 ` Giovanni Biscuolo
2022-05-26 20:40 ` Théo Maxime Tyburn
2022-05-27 6:45 ` Giovanni Biscuolo
2022-05-27 9:21 ` Théo Maxime Tyburn
2022-09-02 16:13 ` Simon Streit
2022-10-06 14:00 ` Ludovic Courtès
2022-10-26 11:24 ` Théo Tyburn
2022-05-30 15:33 ` Ludovic Courtès
2022-06-03 22:04 ` Théo Maxime Tyburn
2022-06-07 17:42 ` Kaelyn
2022-06-08 11:15 ` Kaelyn
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='pnU7824Wd9EPFc7dPtHHD0mWRtKEVnNXYgk42hy1f3dJGptV7ToSv7cyF9j2toTLn853jMQAuofOR_u5NDS5hVpC99cEaNfIa60FpT6GyH0=@protonmail.com' \
--to=rprior@protonmail.com \
--cc=g@xelera.eu \
--cc=guix-devel@gnu.org \
--cc=guix-maintainers@gnu.org \
--cc=jsoo1@asu.edu \
--cc=ludo@gnu.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/guix.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).