From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: 27297@debbugs.gnu.org
Subject: bug#27297: [PATCH] doc: Correction of function name.
Date: Fri, 9 Jun 2017 17:15:24 +0200 [thread overview]
Message-ID: <20170609171524.0badfa4b@alma-ubu> (raw)
From 82405dba978d051eb5ae9614a88f8a07f5fe1e85 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bj=C3=B6rn=20H=C3=B6fling?=
<bjoern.hoefling@bjoernhoefling.de>
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
-@code{specification->package-output} look up the corresponding package
+@code{specification->package+output} look up the corresponding package
objects, like this:
@example
--
2.7.4
next reply other threads:[~2017-06-09 15:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 15:15 Björn Höfling [this message]
2017-06-11 21:18 ` bug#27297: [PATCH] doc: Correction of function name Ludovic Courtès
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=20170609171524.0badfa4b@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=27297@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 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).