all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Théo Maxime Tyburn" <theo.tyburn@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Kaelyn <kaelyn.alexi@protonmail.com>,
	Giovanni Biscuolo <g@xelera.eu>,
	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: Sat, 04 Jun 2022 00:04:25 +0200	[thread overview]
Message-ID: <8735gl5r0z.fsf@gmail.com> (raw)
In-Reply-To: <87h7572fym.fsf@gnu.org>

Hi all,

> Would you be willing to coordinate work on Emacs-Guix for some time?
> If so, I’m in favor of granting you commit access so you can first push
> these four commits, and eventually apply patches that are submitted or
> fix bugs here and there.
>
> If Giovanni or Théo wants to do that, that’s fine too.  What we need is
> to make sure one of us/you can commit some time going forward to at
> least protect Emacs-Guix from bitrot, and ideally help improve it, as
> time permits.
>
> WDYT?

I can definitly participate in this. I wanted to add some functionalities myself anyway so
I think that would make sense. I am stil a beginner guix developer
though so I might not be able to solve intricated bugs. But have
my fare share of elisp hacking so I can probably solve the easy
ones. Hacking emacs-guix also seems like a nice way to start hacking
guix to mee.

> Bug reports would still go to <https://issues.guix.gnu.org>, which you
> can access from the comfort of your Emacs with M-x debbugs-gnu.  :-)

That would be my first time using it, but it sounds like a nice tool.

> Thanks,
> Ludo’.

Thanks,
Théo


  reply	other threads:[~2022-06-03 22:19 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
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 [this message]
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=8735gl5r0z.fsf@gmail.com \
    --to=theo.tyburn@gmail.com \
    --cc=g@xelera.eu \
    --cc=guix-devel@gnu.org \
    --cc=guix-maintainers@gnu.org \
    --cc=kaelyn.alexi@protonmail.com \
    --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.