all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: 45403@debbugs.gnu.org
Subject: [bug#45403] [PATCH] gnu: zfs: Split into packages specific for each of our major supported kernel versions.
Date: Thu, 24 Dec 2020 15:41:33 -0500	[thread overview]
Message-ID: <X+T8/SrQ4hHlHJye@jasmine.lan> (raw)
In-Reply-To: <QOni976E4oF_Bx56oc2L5Im9eQEULdkhOEMfWenhX2u8POiAbkToPuAPRxLZt9jwivFuFe10BGkmc_-a1iInMYU9aBNopFeILMWrfzYKhEU=@protonmail.com>

On Thu, Dec 24, 2020 at 10:59:56AM +0000, raid5atemyhomework via Guix-patches via wrote:
> Fixes: https://issues.guix.gnu.org/45401
> 
> Untested --- no idea how to repoint my guix to a temporary commit on my local file repo, would appreciate any guidance.

There are primarily two ways to use Guix with a local Git repo.

First, you can follow the instructions in the manual section
Contributing, specifically the sections Building from Git and Running
Guix Before It Is Installed.

Or, you can use something like `guix pull --url=/path/to/my/repo
--commit=mycommit`.

Beyond that, does this patch create linux-libre packages with ZFS
support compiled in?




  reply	other threads:[~2020-12-24 20:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-24 10:59 [bug#45403] [PATCH] gnu: zfs: Split into packages specific for each of our major supported kernel versions raid5atemyhomework via Guix-patches via
2020-12-24 20:41 ` Leo Famulari [this message]
2020-12-25  1:12 ` raid5atemyhomework via Guix-patches via
2020-12-25  4:09   ` Tobias Geerinckx-Rice via Guix-patches via
2021-01-04 13:58     ` Danny Milosavljevic
2021-01-04 15:49       ` raid5atemyhomework via Guix-patches via
2021-01-04 16:07         ` raid5atemyhomework via Guix-patches via
2021-01-04 16:32           ` raid5atemyhomework via Guix-patches via
2021-01-08 15:50 ` bug#45403: " raid5atemyhomework via Guix-patches via

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=X+T8/SrQ4hHlHJye@jasmine.lan \
    --to=leo@famulari.name \
    --cc=45403@debbugs.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.