all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Tobias Geerinckx-Rice <tobias.geerinckx.rice@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: btrfs-progs: Update to 4.4.1.
Date: Thu, 3 Mar 2016 22:44:37 -0500	[thread overview]
Message-ID: <20160304034437.GA2484@jasmine> (raw)
In-Reply-To: <CAKFHe2Qkaqkd=3Rzhjtfcja-LN5rBqCo=-mj3iQkeaZMj3qz4w@mail.gmail.com>

On Fri, Mar 04, 2016 at 04:08:01AM +0100, Tobias Geerinckx-Rice wrote:
> On 28/02/2016, Leo Famulari <leo@famulari.name> wrote:
> > On Sat, Feb 27, 2016 at 10:41:42PM +0200, Efraim Flashner wrote:
> >> On Sat, 27 Feb 2016 01:17:04 +0100
> >> Tobias Geerinckx-Rice <tobias.geerinckx.rice@gmail.com> wrote:
> >>
> >> > * gnu/packages/linux.scm (btrfs-progs): Update to 4.4.1.
> >
> >> looks good to me!
> >>
> >> applied in 9c7f7e2d.
> >
> > Thanks for keeping up with this pcakage, Tobias!
> >
> > Have you had a chance to investigate how to include it in the initrd?
> >
> > https://lists.gnu.org/archive/html/guix-devel/2016-02/msg00489.html
> [Lynx won't let me remove lines. Nice. At least I'm on GuixSD]
> 
> Hullo Leo,
> 
> Sorry, not yet. I've had no free time lately. I hope the
> coming week will bring some. Either way, 0.9.1 won't yet
> have much butter in it.
> 
> I'll try writing a static package expression before diving
> into the initrd, which I'm guessing is quite different from
> that of your average Linux distribution...

Okay, feel free to share your work as you go! I'll probably make an
attempt as well, although I can't say exactly when.

      reply	other threads:[~2016-03-04  3:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-27  0:17 [PATCH] gnu: btrfs-progs: Update to 4.4.1 Tobias Geerinckx-Rice
2016-02-27 20:41 ` Efraim Flashner
2016-02-27 23:27   ` Leo Famulari
2016-03-04  3:08     ` Tobias Geerinckx-Rice
2016-03-04  3:44       ` Leo Famulari [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160304034437.GA2484@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=tobias.geerinckx.rice@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 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.