Linux NFS development
 help / color / mirror / Atom feed
From: Gioele Barabucci <gioele@svario.it>
To: linux-nfs@vger.kernel.org
Cc: Steve Dickson <steved@redhat.com>, Gioele Barabucci <gioele@svario.it>
Subject: [PATCH v2 0/3] Typos and documentation fixes
Date: Thu,  4 Jan 2024 09:25:25 +0100	[thread overview]
Message-ID: <20240104082528.1425699-1-gioele@svario.it> (raw)

Hi,

the following three patches fix a few typos detected by Debian's QA tool
lintian. The last patch also adds Documentation= options to various
service files.

--
v2: rebased on top of 2.7.1-rc3, added S-o-B trailers

Regards, 

Gioele Barabucci (3):
  Fix typos in error messages
  Fix typos in manpages
  systemd: Add Documentation= option to service units

 support/export/export.c           | 2 +-
 support/export/v4root.c           | 2 +-
 systemd/nfs-blkmap.service        | 1 +
 systemd/nfs-idmapd.service        | 1 +
 systemd/nfs-mountd.service        | 1 +
 systemd/nfs-server.service        | 1 +
 systemd/nfsdcld.service           | 1 +
 systemd/rpc-gssd.service.in       | 1 +
 systemd/rpc-statd-notify.service  | 1 +
 systemd/rpc-statd.service         | 1 +
 systemd/rpc-svcgssd.service       | 1 +
 utils/exportfs/exports.man        | 2 +-
 utils/mount/mount_libmount.c      | 2 +-
 utils/mount/nfs.man               | 4 ++--
 utils/mount/nfsmount.conf.man     | 2 +-
 utils/nfsdcld/nfsdcld.man         | 2 +-
 utils/nfsdcltrack/nfsdcltrack.man | 2 +-
 17 files changed, 18 insertions(+), 9 deletions(-)

-- 
2.43.0


             reply	other threads:[~2024-01-04  8:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-04  8:25 Gioele Barabucci [this message]
2024-01-04  8:25 ` [PATCH v2 1/3] Fix typos in error messages Gioele Barabucci
2024-01-04  8:25 ` [PATCH v2 2/3] Fix typos in manpages Gioele Barabucci
2024-01-04  8:25 ` [PATCH v2 3/3] systemd: Add Documentation= option to service units Gioele Barabucci
2024-01-23 15:17 ` [PATCH v2 0/3] Typos and documentation fixes Steve Dickson

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240104082528.1425699-1-gioele@svario.it \
    --to=gioele@svario.it \
    --cc=linux-nfs@vger.kernel.org \
    --cc=steved@redhat.com \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox