[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
01/08: doc: Fix typos.
From: |
Alex Kost |
Subject: |
01/08: doc: Fix typos. |
Date: |
Sat, 28 Jan 2017 09:42:09 +0000 (UTC) |
alezost pushed a commit to branch master
in repository guix.
commit f31f1acac2efb4bc6558b604a07b56f826423177
Author: Alex Kost <address@hidden>
Date: Tue Jan 24 16:52:56 2017 +0300
doc: Fix typos.
* doc/guix.texi: Use "@" for package specifications.
---
doc/guix.texi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/guix.texi b/doc/guix.texi
index 19d7f28..719ebd9 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -4511,7 +4511,7 @@ guix build --quiet --keep-going \
@var{package-or-derivation} may be either the name of a package found in
the software distribution such as @code{coreutils} or
address@hidden, or a derivation such as
address@hidden@8.20}, or a derivation such as
@file{/gnu/store/@dots{}-coreutils-8.19.drv}. In the former case, a
package with the corresponding name (and optionally version) is searched
for among the GNU distribution modules (@pxref{Package Modules}).
@@ -5671,7 +5671,7 @@ single output for a package that could easily be split
(@pxref{Packages
with Multiple Outputs}). Such are the typical issues that
@command{guix size} can highlight.
-The command can be passed a package specification such as @code{gcc-4.8}
+The command can be passed a package specification such as @address@hidden
or @code{guile:debug}, or a file name in the store. Consider this
example:
- branch master updated (aaf111a -> c695ed3), Alex Kost, 2017/01/28
- 04/08: gnu: Add emacs-ht., Alex Kost, 2017/01/28
- 01/08: doc: Fix typos.,
Alex Kost <=
- 06/08: gnu: Add emacs-gntp., Alex Kost, 2017/01/28
- 08/08: gnu: Add emacs-mu4e-alert., Alex Kost, 2017/01/28
- 03/08: gnu: tvtime: Update to 1.0.11., Alex Kost, 2017/01/28
- 07/08: gnu: Add emacs-alert., Alex Kost, 2017/01/28
- 02/08: gnu: manaplus: Update to 1.7.1.21., Alex Kost, 2017/01/28
- 05/08: gnu: Add emacs-log4e., Alex Kost, 2017/01/28