--- Begin Message ---
Subject: |
[PATCH] doc: Correction of function name. |
Date: |
Fri, 9 Jun 2017 17:15:24 +0200 |
From 82405dba978d051eb5ae9614a88f8a07f5fe1e85 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bj=C3=B6rn=20H=C3=B6fling?=
<address@hidden>
Date: Thu, 8 Jun 2017 08:57:55 +0200
Subject: [PATCH] doc: Correction of function name.
* doc/guix.texi (Invoking guix package): Correct function name.
---
doc/guix.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/guix.texi b/doc/guix.texi
index a5b7875..0b2aed2 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -1724,7 +1724,7 @@ In this example we have to know which modules
define the @code{emacs} and @code{guile-2.0} variables to provide the
right @code{use-package-modules} line, which can be cumbersome. We can
instead provide regular package specifications and let
address@hidden>package-output} look up the corresponding package
address@hidden>package+output} look up the corresponding package
objects, like this:
@example
--
2.7.4
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#27297: [PATCH] doc: Correction of function name. |
Date: |
Sun, 11 Jun 2017 23:18:11 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) |
Hi Björn,
Björn Höfling <address@hidden> skribis:
> From 82405dba978d051eb5ae9614a88f8a07f5fe1e85 Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?Bj=C3=B6rn=20H=C3=B6fling?=
> <address@hidden>
> Date: Thu, 8 Jun 2017 08:57:55 +0200
> Subject: [PATCH] doc: Correction of function name.
>
> * doc/guix.texi (Invoking guix package): Correct function name.
Good catch… though the just-pushed commit
c08ea55e7ec25261e4596bf6726a83c1ed056b94 introduces
‘specifications->manifest’ for this particular use case.
Thanks,
Ludo’.
--- End Message ---