unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <othacehe@gnu.org>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: 55602-done@debbugs.gnu.org
Subject: bug#55602: [PATCH 0/2] Move (gnu platform) and friends to guix, and fix linux module build system.
Date: Wed, 25 May 2022 09:31:07 +0200	[thread overview]
Message-ID: <877d6axe4k.fsf@gnu.org> (raw)
In-Reply-To: <20220523202902.32411-1-dev@jpoiret.xyz> (Josselin Poiret's message of "Mon, 23 May 2022 22:29:02 +0200")


Hello,

> knows syntax expands at compile/expand-time only.  Since the platform
> code has moved to its own cozy (gnu platform) in the meantime, I
> figured that it could very well be simply use-module'd, but then it'd
> have to end up in (guix ...) to follow the rule that guix modules
> should never directly use-module gnu modules.  Hence this quite big
> patchset.

Oops sorry for not noticing it, pushed!

Thanks,

Mathieu




      parent reply	other threads:[~2022-05-25  7:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23 20:29 [bug#55602] [PATCH 0/2] Move (gnu platform) and friends to guix, and fix linux module build system Josselin Poiret via Guix-patches via
2022-05-23 20:37 ` [bug#55602] [PATCH v2 " Josselin Poiret via Guix-patches via
2022-05-23 20:37   ` [bug#55602] [PATCH v2 1/2] Move (gnu platform) and (gnu platforms ...) to guix/ Josselin Poiret via Guix-patches via
2022-05-23 20:37   ` [bug#55602] [PATCH v2 2/2] build-system: linux-module: Directly use-module (guix platform) Josselin Poiret via Guix-patches via
2022-05-25  7:31 ` Mathieu Othacehe [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=877d6axe4k.fsf@gnu.org \
    --to=othacehe@gnu.org \
    --cc=55602-done@debbugs.gnu.org \
    --cc=dev@jpoiret.xyz \
    /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).