[PATCH] doc: Fix `copy-recursively' arguments.

  • Done
  • quality assurance status badge
Details
2 participants
  • aurtzy
  • Ludovic Courtès
Owner
unassigned
Submitted by
aurtzy
Severity
normal
A
A
aurtzy wrote on 12 Nov 07:56 +0100
(address . guix-patches@gnu.org)(name . aurtzy)(address . aurtzy@gmail.com)
b93efe39bdeb37b0d7c177f738a412122e0933b8.1731394560.git.aurtzy@gmail.com
The `select?' keyword is part of the description instead of immediately
following `keep-permissions?' in the arguments list for `copy-recursively'.
This adds a missing '@' to fix that.

* doc/guix.texi (Build Utilities): Fix `copy-recursively' arguments.

Change-Id: If6802490a6afebc884b039d84f1fe4f9202a1151
---
doc/guix.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

Toggle diff (17 lines)
diff --git a/doc/guix.texi b/doc/guix.texi
index 8f65387e92..9d349d328c 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -10648,7 +10648,7 @@ Build Utilities
@deffn {Procedure} copy-recursively source destination @
[#:log (current-output-port)] [#:follow-symlinks? #f] @
- [#:copy-file copy-file] [#:keep-mtime? #f] [#:keep-permissions? #t]
+ [#:copy-file copy-file] [#:keep-mtime? #f] [#:keep-permissions? #t] @
[#:select? (const #t)]
Copy @var{source} directory to @var{destination}. Follow symlinks if
@var{follow-symlinks?} is true; otherwise, just preserve them. Call

base-commit: b790db7589858fc77989b4d1f369c52bca6d6e7c
--
2.46.0
L
L
Ludovic Courtès wrote on 12 Nov 23:29 +0100
(name . aurtzy)(address . aurtzy@gmail.com)
87ttccrsqp.fsf@gnu.org
aurtzy <aurtzy@gmail.com> skribis:

Toggle quote (8 lines)
> The `select?' keyword is part of the description instead of immediately
> following `keep-permissions?' in the arguments list for `copy-recursively'.
> This adds a missing '@' to fix that.
>
> * doc/guix.texi (Build Utilities): Fix `copy-recursively' arguments.
>
> Change-Id: If6802490a6afebc884b039d84f1fe4f9202a1151

Applied, thanks!
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 74321@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 74321
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch