unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Diego Nicola Barbato <dnbarbato@posteo.de>
To: 35661@debbugs.gnu.org
Subject: [bug#35661] [PATCH] doc: Fix typo.
Date: Thu, 09 May 2019 23:19:54 +0200	[thread overview]
Message-ID: <87imujpbph.fsf@GlaDOS.home> (raw)

[-- Attachment #1: Type: text/plain, Size: 233 bytes --]

Hi Guix,

The documentation of 'shepherd-service' erroneously calls the
'requirement' field 'requirements'.  The attached patch fixes that.

I have also noticed that the 'auto-start?' field is not mentioned at
all.

Regards,

Diego


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-doc-Fix-typo.patch --]
[-- Type: text/x-patch, Size: 916 bytes --]

From 635fa669c8d52afd2363c99bfa03b2315af29e74 Mon Sep 17 00:00:00 2001
From: Diego Nicola Barbato <dnbarbato@posteo.de>
Date: Thu, 9 May 2019 22:44:45 +0200
Subject: [PATCH] doc: Fix typo.

* doc/guix.texi (shepherd-service): 'requirement' instead of 'requirements'.
---
 doc/guix.texi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/guix.texi b/doc/guix.texi
index df7208229c..f88fa827d4 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -25279,7 +25279,7 @@ These are the names that may be passed to @command{herd start},
 shepherd, The GNU Shepherd Manual}).  @xref{Slots of services, the
 @code{provides} slot,, shepherd, The GNU Shepherd Manual}, for details.
 
-@item @code{requirements} (default: @code{'()})
+@item @code{requirement} (default: @code{'()})
 List of symbols denoting the Shepherd services this one depends on.
 
 @cindex one-shot services, for the Shepherd
-- 
2.21.0


             reply	other threads:[~2019-05-09 21:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-09 21:19 Diego Nicola Barbato [this message]
2019-05-11  7:44 ` bug#35661: [PATCH] doc: Fix typo Arun Isaac
2019-05-11 15:45   ` [bug#35661] " Diego Nicola Barbato
2019-05-11 22:20     ` Arun Isaac

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=87imujpbph.fsf@GlaDOS.home \
    --to=dnbarbato@posteo.de \
    --cc=35661@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).