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: Kaelyn <kaelyn.alexi@protonmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
	"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: Thu, 26 May 2022 22:40:57 +0200	[thread overview]
Message-ID: <871qwgvxgm.fsf@gmail.com> (raw)
In-Reply-To: <B033gqo3WlVWTqmEMM9k_dpVIn_-6Ovuqj-L5t5NnnkwBBV1CSvztgEj3-mME5-0UX3YR81oGhyq1tMgfB7VqL7AgVOe2R_HzVk9tjfwlII=@protonmail.com> (Kaelyn's message of "Mon, 23 May 2022 15:36:35 +0000")

Hi,

I would also be happy to help if I can.

I could create a new branch starting at savannah’s HEAD and
cherry pick everything relevant from gitlab since the merge-base. That
would probably be everything except the duplicates, so the 4 commit
Kaelyn mentioned, right ?

Probably we also need to gather the issues from gitlab. Not experienced
with savannah issue tracker, but I could try it out. 

Cheers,

Théo

Kaelyn <kaelyn.alexi@protonmail.com> writes:

> Hi,
>
> ------- Original Message -------
> On Monday, May 23rd, 2022 at 7:39 AM, Ludovic Courtès <ludo@gnu.org> wrote:
>
>
>> Hi,
>>
>> Ludovic Courtès ludo@gnu.org skribis:
>>
>> > 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.
>>
>>
>> Emailed Alex off-list and didn’t get a reply.
>>
>> So we’re on our own like grownups, but that’s fine, I’m sure we’ll
>> manage. :-)
>>
>> First, we need to cherry-pick relevant commits from gitlab.com. Any
>> takers? If you Giovanni or anyone else is willing to help, we can grant
>> commit access so we share the work. Another way to help is by listing
>> commits that should be applied.
>>
>> Volunteers?
>
> I'd be happy to help with the efforts! 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>
>
> Cheers,
> Kaelyn
>
> P.S For full reference, the remotes are:
> gitlab	https://gitlab.com/emacs-guix/emacs-guix.git
> official	git://git.savannah.gnu.org/guix/emacs-guix.git
>
> `git merge-base gitlab/master official/master` returns the hash:
> 41fba4eec845e050be92bfe76c0f7980bbe821bd
>
> The commits since the merge-base in the savannah repo:
> * c9c5cb0 - (HEAD -> master, official/master) elisp/profiles: Support Home profiles. (3 months ago)<Ludovic Courtès>
> * 94fcf1f - elisp/prettify: Recognize "/zstd" in nar URLs. (4 months ago)<Ludovic Courtès>
> * 825ab77 - Remove all references to the GuixSD name. (1 year, 4 months ago)<Tobias Geerinckx-Rice>
> * a42f66c - elisp: Support geiser @0.12.x (1 year, 4 months ago)<John Soo>
> * d61d827 - scheme: Remove @@ for Guile 3.x support. (1 year, 4 months ago)<John Soo>
>
> And the commits in the gitlab repo since the merge-base:
> * 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>
> * 057e3a6 - Remove all references to the "GuixSD" name (1 year, 4 months ago)<Tobias Geerinckx-Rice>
> * bb2a053 - elisp/repl: Support geiser 0.12.x (1 year, 5 months ago)<John Soo>
> * 753dbb0 - scheme: Remove "@@" from 'log-url' (1 year, 5 months ago)<John Soo>
> * 66695d0 - scheme: Remove "@@" from "pack" symbols (1 year, 5 months ago)<John Soo>
> * 20cb235 - scheme: Remove "@@" from 'operating-system-firmware' (1 year, 5 months ago)<John Soo>
> * 307aa05 - scheme: Remove "@@" from 'search-path-environment-variables' (1 year, 5 months ago)<John Soo>
>
>>
>> Thanks,
>> Ludo’.


  parent reply	other threads:[~2022-05-26 20:42 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 [this message]
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=871qwgvxgm.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.