From: Kaelyn <kaelyn.alexi@protonmail.com>
To: guix-devel@gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>,
"Giovanni Biscuolo" <g@xelera.eu>,
"Théo Maxime Tyburn" <theo.tyburn@gmail.com>,
"GNU Guix maintainers" <guix-maintainers@gnu.org>
Subject: Re: emacs-guix (upstream) needs more love: a survey of repositories, homepage and issues
Date: Wed, 08 Jun 2022 11:15:48 +0000 [thread overview]
Message-ID: <RKWS9lijlNKJIt4jGisLwRygUYDQMJ7IZ-txRrz6ctTQ51M5ux1cDr9Abqr0Nf1C7TLFq1qGF37LA0agJuWr7RGSlIxaWqupaqVh8-ZgweU=@protonmail.com> (raw)
In-Reply-To: <lhEGDJ-5q64ILoPKz_OvkIIb5dnDf9BmIWC4SG0tk1wYIUYGgOwi8j-a0x64PxhUetgccn9WOSr5CwDCkzReWJbyDxkj2jPO1j6Iwg1EMbs=@protonmail.com>
On Tuesday, June 7th, 2022 at 10:42 AM, Kaelyn <kaelyn.alexi@protonmail.com> wrote:
[snip]
> > > I just took a few minutes and checked both repos out into a single
> > > working tree, and there aren't many commits unique to each
> > > repository. The official savannah repo has 5 commits since they
> > > diverged, with the 3 oldest looking like variations of the 6 oldest in
> > > the gitlab repo. Likewise, not counting the 6 just mentioned, there
> > > are 4 unique commits in the gitlab repo. Those 4 commits are:
> > >
> > > * c9aef52 - (gitlab/master, gitlab/HEAD) elisp/ui-package: Add 'guix-package-use-name-at-point' variable (12 months ago)<Alex Kost>
> > > * e5ff0e5 - elisp/ui-package: Fix an error on package name read (12 months ago)<Alex Kost>
> > > * 8ce6d21 - Rename 'guix-search-…' to 'guix-packages-…' commands (1 year, 3 months ago)<Alex Kost>
> > > * fbc2bbc - elisp/ui-package: Use thing at point for 'guix-packages-by-name' command (1 year, 3 months ago)<Alex Kost>
> >
> > Awesome.
> >
> > 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?
>
>
> While my time can sometimes be a little spotty short-term, I am willing to coordinate work on Emacs-Guix and at least protect it from bitrot. Right now, I'm still fairly new to Emacs and am still working on my setup and learning & integrating things like using Emacs-Guix or M-x debbugs-gnu, but I also wish to both get more involved with Guix and improve my Emacs development and debugging skills. I'll also be happy to push those four commits once I work out my local build and testing (i.e. getting the tests to pass locally with a clean tree to see if my cherry-picking of the commits are the reason tests are failing.)
I want to give a quick update: I have successfully built and run "make check" for my local branch with the four cherry-picked commits, plus one addition commit to fix the build (an emacs script used for local builds was passing an argument to guix-emacs-autoload-packages, which was refactored to not take arguments in guix commit 47b3b4c2aa from 2019). With my extra commit, I think the branch should be ready to push.
Cheers,
Kaelyn
prev parent reply other threads:[~2022-06-08 11:17 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
2022-06-07 17:42 ` Kaelyn
2022-06-08 11:15 ` Kaelyn [this message]
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='RKWS9lijlNKJIt4jGisLwRygUYDQMJ7IZ-txRrz6ctTQ51M5ux1cDr9Abqr0Nf1C7TLFq1qGF37LA0agJuWr7RGSlIxaWqupaqVh8-ZgweU=@protonmail.com' \
--to=kaelyn.alexi@protonmail.com \
--cc=g@xelera.eu \
--cc=guix-devel@gnu.org \
--cc=guix-maintainers@gnu.org \
--cc=ludo@gnu.org \
--cc=theo.tyburn@gmail.com \
/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).