From: Tobias Geerinckx-Rice <me@tobias.gr>
To: John Soo <jsoo1@asu.edu>
Cc: guix-devel@gnu.org
Subject: Re: Emacs-Guix repository location moved to Savannah
Date: Tue, 12 Jan 2021 16:02:46 +0100 [thread overview]
Message-ID: <87mtxenqp5.fsf@nckx> (raw)
In-Reply-To: <87k0si445c.fsf@asu.edu>
[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]
John Soo 写道:
> Does it still not start? As of (guix) commit
> f98e3adcd533a4a4c5482343a26d01076e946f92 I at least can start a
> repl
> without a crash.
Good to know. I'll try again and let you know.
>> Where do you accept patches? The one below is untested.
>
> That's also a good question. I would prefer to use the existing
> guix-patches. Is that ok by the standard mailing list
> administrators?
I can't think of a better place nor can I imagine we'll be
overwhelmed by emacs-guix patches.
(And if we are, that's probably a good thing at this point?)
> As to the patch, I would like to apply it. Is Guix System still
> the
> preferred name?
Yep. There's also no separate ‘System’ logo anymore[0]. Guix
System being merely a different earthly manifestation of the one
eternal Guix.
> I thought another renaming took place. I am possibly
> very out of date on that info though.
Nope.
Kind regards,
T G-R
[0]: http://guix.gnu.org/en/graphics/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2021-01-12 15:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 14:51 Emacs-Guix repository location moved to Savannah John Soo
2021-01-12 2:02 ` Ryan Prior
2021-01-12 14:38 ` John Soo
2021-01-12 9:04 ` Pierre Neidhardt
2021-01-12 14:20 ` John Soo
2021-01-12 14:39 ` John Soo
2021-01-12 14:46 ` Pierre Neidhardt
2021-01-12 10:48 ` Tobias Geerinckx-Rice
2021-01-12 14:32 ` John Soo
2021-01-12 15:02 ` Tobias Geerinckx-Rice [this message]
2021-01-12 15:17 ` John Soo
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=87mtxenqp5.fsf@nckx \
--to=me@tobias.gr \
--cc=guix-devel@gnu.org \
--cc=jsoo1@asu.edu \
/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).