From: wolf <wolf@wolfsden.cz>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: help-guix@gnu.org
Subject: Re: How to create and maintain a personal Guix fork?
Date: Mon, 25 Sep 2023 15:06:56 +0200 [thread overview]
Message-ID: <ZRGF8BBQn3lOr3Mh@ws> (raw)
In-Reply-To: <CAFHYt55Zd9jY=-_R_HdDR-XBoVssmNiMiKxH+p9YnG9oXkepPA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]
On 2023-09-05 09:18:45 -0700, Felix Lechner wrote:
> Hi Wolf,
>
> On Sun, Sep 3, 2023 at 11:31 AM wolf <wolf@wolfsden.cz> wrote:
> >
> > I would like to start my own fork of the upstream Guix
>
> That's great news! I think it's the only way to contribute important
> changes to Guix. You may find some helpful information at the end of
> this message:
>
> https://lists.gnu.org/archive/html/guix-devel/2023-08/msg00121.html
>
> I pull unauthenticated right now but should probably add my key to
> 'lechner-experimental' on Codeberg. Thanks!
In the end more steps were required than I expected. And the signing sadly
required patching git-authenticate.scm in the fork. I put together a script
that automates this process, maybe it will be useful to others as well:
https://git.sr.ht/~graywolf/guix/tree/master/item/etc/fork-guix
>
> Kind regards
> Felix
>
> P.S. Perhaps you meant to force a reply to the list alone. I copied you, anyway.
Have a nice day,
W.
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-09-25 13:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-03 18:31 How to create and maintain a personal Guix fork? wolf
2023-09-05 16:18 ` Felix Lechner via
2023-09-25 13:06 ` wolf [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=ZRGF8BBQn3lOr3Mh@ws \
--to=wolf@wolfsden.cz \
--cc=felix.lechner@lease-up.com \
--cc=help-guix@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.
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).