From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>, "Giovanni Biscuolo" <g@xelera.eu>
Cc: guix-devel@gnu.org, GNU Guix maintainers <guix-maintainers@gnu.org>
Subject: Re: emacs-guix (upstream) needs more love: a survey of repositories, homepage and issues
Date: Fri, 29 Apr 2022 12:12:43 +0200 [thread overview]
Message-ID: <87levoci5g.fsf@gmail.com> (raw)
In-Reply-To: <877d79fx4e.fsf@gnu.org>
Hi,
On Thu, 28 Apr 2022 at 10:08, Ludovic Courtès <ludo@gnu.org> wrote:
> I’m not sure what “personal” means in this case.
Quoting [1]:
From: Alex Kost <alezost@gmail.com>
To: John Soo <jsoo1@asu.edu>
Cc: Guix-Devel <guix-devel@gnu.org>
Subject: Re: New emacs-guix location
Date: Tue, 22 Dec 2020 13:20:59 +0300
John Soo (2020-11-24 11:23 -0800) wrote:
> Hello Alex and Guix,
> Hope you are well.
Hello, I am fine, thanks!
> I volunteered to maintain some version of
> emacs-guix recently. How do you feel about a fork moving to Savannah?
You (and all the Guix people) are free to do whatever you think is
appropriate. Emacs-Guix is a free software after all.
So if you will maintain the "official" (used by Guix) version of
Emacs-Guix at Savannah, I will only be happy that I don't have this
burden anymore.
As for me, I will continue to use my version of Emacs-Guix and to adjust
it for my needs.
And thank you for your latest commits that fixed Emacs-Guix for the
current versions of Guix and Geiser!
1: <https://yhetil.org/guix/87v9cum99w.fsf@gmail.com>
> Anyway, the situation is confusing; there’s no point in having two
> slightly different variants. I suggest we check with Alex off-list to
> get a better understanding of what they want. Worst case, we can
> cherry-pick commits from Alex’s copy if Alex doesn’t want to be involved
> in discussions around Emacs-Guix or Guix development.
To add to the confusion, note that this Gitlab repo [2] also contains
some issues. But both Gitlab and Github repos are sync by Alex, I
guess.
BTW, note this message [3] by Alex on April 2020:
I am very sorry but I rarely use Guix and Emacs-Guix these days and I
don't have any wish to maintain it. I mean, if it is some small
easy-to-fix problem or a proposed patch, then I will look at it, but
investigating a problem like this is too much for me currently. Sorry :-(
Hopefully, someone else who has this problem will look at it.
3: <https://github.com/alezost/guix.el/issues/38#issuecomment-617718043>
and I sent them an email off-list asking them the status on 29 May 2020,
15:33. And I am not able to find an answer back.
Cheers,
simon
2: <https://gitlab.com/emacs-guix/emacs-guix>
next prev parent reply other threads:[~2022-04-29 11:15 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87levoci5g.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=g@xelera.eu \
--cc=guix-devel@gnu.org \
--cc=guix-maintainers@gnu.org \
--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 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.