Attachment 67114 Details for Bug 54501 – Typo fixes for loginctl.xml (v2)

[patch] Typo fixes for loginctl.xml (v2)

0001-docs-typos-in-loginctl.xml.patch (text/plain), 1.44 KB, created by Thomas H.P. Andersen on 2012-09-13 19:18:52 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Thomas H.P. Andersen

Created: 2012-09-13 19:18:52 UTC

Size: 1.44 KB

patch

obsolete

>From fb981487d99411be288904091bbae7679eb98f3d Mon Sep 17 00:00:00 2001
>From: Thomas Hindoe Paaboel Andersen <phomes@gmail.com>
>Date: Thu, 13 Sep 2012 21:09:44 +0200
>Subject: [PATCH] docs: typos in loginctl.xml
>
>---
> man/loginctl.xml | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
>diff --git a/man/loginctl.xml b/man/loginctl.xml
>index b0266e9..7d9d8a1 100644
>--- a/man/loginctl.xml
>+++ b/man/loginctl.xml
>@@ -88,7 +88,7 @@
>                                 <term><option>-p</option></term>
> 
>                                 <listitem><para>When showing
>-                                session/user/ properties, limit
>+                                session/user properties, limit
>                                 display to certain properties as
>                                 specified as argument. If not
>                                 specified all set properties are
>@@ -403,7 +403,7 @@
>                                 paths in the <filename>/sys</filename>
>                                 file system. To create a new seat
>                                 attach at least one graphics card to a
>-                                previously unused seat names. seat
>+                                previously unused seat name. seat
>                                 names may consist only of a-z, A-Z,
>                                 0-9, "-" and "_" and must be prefixed
>                                 with "seat". To drop assignment of a
>-- 
>1.7.12
>

Actions: View | Splinter Review

Attachments on bug 54501: 66618 | 66699 | 66746 | 66936 | 66999 | 67114

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.