all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ryan Prior <ryanprior@hey.com>
To: Development of GNU Guix and the GNU System distribution
	<guix-devel@gnu.org>, John Soo <jsoo1@asu.edu>
Subject: Re: Emacs-Guix repository location moved to Savannah
Date: Tue, 12 Jan 2021 02:02:51 +0000	[thread overview]
Message-ID: <7c4902a9814c9e91e093659445179d231435846d@hey.com> (raw)
In-Reply-To: <871rer5xxv.fsf@asu.edu>

[-- Attachment #1: Type: text/plain, Size: 848 bytes --]

On January 11, 2021, John Soo <jsoo1@asu.edu> wrote:
> Hi Guix!
>
> Emacs-Guix has a new home! I just pushed
> a42f66cb40a9e60611f429a403b08dbed29bae02 to Emacs-Guix on Savannah.

Thanks and congrats!

> If you have a command you want fixed, please let me know and I will
> priortize it.

How do you feel about removing commands that nobody feels like fixing?
It might help Emacs-Guix build a reputation for reliability.

> What do you think about having conversations about Emacs-Guix on guix-
> devel?

I think it's a good idea. Conversing regularly on this list will keep
people abreast of what state things are in. Moving conversation to a
dedicated channel likely means nobody would read, which disincentivizes
writing. If discussion on this list reaches a level of volume where it's
annoying, that's the signal to explore alternate channels.

[-- Attachment #2: Type: text/html, Size: 3229 bytes --]

  reply	other threads:[~2021-01-12  2:03 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7c4902a9814c9e91e093659445179d231435846d@hey.com \
    --to=ryanprior@hey.com \
    --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 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.