From: Giovanni Biscuolo <g@xelera.eu>
To: "Ludovic Courtès" <ludo@gnu.org>
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: Thu, 28 Apr 2022 18:27:28 +0200 [thread overview]
Message-ID: <87levpgolr.fsf@xelera.eu> (raw)
In-Reply-To: <877d79fx4e.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1716 bytes --]
Hi Ludovic:
Ludovic Courtès <ludo@gnu.org> writes:
> Hi Giovanni,
>
> Giovanni Biscuolo <g@xelera.eu> skribis:
>
>> AFAIU since 2021-01-11 [1] the new official home of emacs-guix is on
>> Savannah as a Guix sub-project [2]; Alex Kost agreed [3] and told us
>> that:
>>
>>
>> As for me, I will continue to use my version of Emacs-Guix and to adjust
>> it for my needs.
>>
>>
>> and that's what he is doing (see below), so now "officially" we have
>> /two/ packages named emacs-guix: the official one at Savannah and the
>> "personal" one maintained by Alex.
>
> I’m not sure what “personal” means in this case.
Just my personal interpretation of the words "my version" and "for my
needs" from Alex :-D... after all Alex's version is now the Guix
"official" one (the one we are packaging)
> 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.
I agree, thank you for your off-list message, let's wait Alex reply.
> 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.
In this worst case, we'll have two different emacs-guix packages,
documentation, issue tracking: the situation will continue to be
confusing, one of the two emacs-guix "ecosystems" (repo, web page, issue
tracking) should be discontinued (or renamed?), IMHO, hopefully with
both Alex and John as co-maintainers in one emacs-guix.
> Thanks for the heads-up!
Thank you all for your work!
Gio'
--
Giovanni Biscuolo
Xelera IT Infrastructures
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]
next prev parent reply other threads:[~2022-04-28 16:28 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87levpgolr.fsf@xelera.eu \
--to=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.