util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Helge Kreutzmann <debian@helgefjell.de>
To: "Mario Blättermann" <mario.blaettermann@gmail.com>
Cc: util-linux@vger.kernel.org
Subject: Re: Errors in man pages of util-linux
Date: Sun, 13 Feb 2022 19:51:04 +0100	[thread overview]
Message-ID: <20220213185104.GA23259@Debian-50-lenny-64-minimal> (raw)
In-Reply-To: <CAHi0vA_7ZWjT=BY7Tc65N4sajBjkKd1LLbd1CmmYPWfgwWvg1A@mail.gmail.com>

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

Hello Mario,
On Sun, Feb 13, 2022 at 07:33:07PM +0100, Mario Blättermann wrote:
> Am Do., 10. Feb. 2022 um 21:35 Uhr schrieb Helge Kreutzmann
> <debian@helgefjell.de>:
> >
> > Hello all,
> > On Thu, Feb 10, 2022 at 08:23:41PM +0100, Helge Kreutzmann wrote:
> > > I will send the issues in individual mails (like last time), without
> > > this header. This will be a total of 84 mails.
> > >
> > > I'll wait with sending for ~ 1 hour in case you would not like to have
> > > them in those e-mails.
> >
> > Mario asked me to provide the issues, therefor I send them to him
> > directly for handling.
> >
> 
> I've fixed most of the issues in my Github fork; see pull request
> #1601. However, there's something left (my comments are in brackets):

Thanks.

My 5 ¢:

> --
> Man page: hwclock.8
> Issue:    date-time → date time??
> 
> "There are two types of date-time clocks:"
> 
> (We have lots of occurences of this "date-time" thing. Don't know
> whether it's good English or bad English …)

It's used quite a few times in the file, so better leave it as is to
be consistent.

> --
> Man page: lsmem.1
> Issue:    The first sentence is broken
> 
> "The B<lsmem> command lists a new memory range always when the current memory "
> "block distinguish from the previous block by some output column. This "
> "default behavior is possible to override by the B<--split> option (e.g., "
> "B<lsmem --split=ZONES>). The special word \"none\" may be used to ignore all "
> "differences between memory blocks and to create as large as possible "
> "continuous ranges. The opposite semantic is B<--all> to list individual "
> 
> (Not sure what this means. I can't remember anymore why I wrote this
> comment more than three years ago …)

Sorry, the english is rather hard to read:
Suggested:
The command B<lsmem> always lists a new memory range when the current
memory block differs from the previous block in some output column.

Greetings

             Helge
-- 
      Dr. Helge Kreutzmann                     debian@helgefjell.de
           Dipl.-Phys.                   http://www.helgefjell.de/debian.php
        64bit GNU powered                     gpg signed mail preferred
           Help keep free software "libre": http://www.ffii.de/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-02-13 18:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 19:23 Errors in man pages of util-linux Helge Kreutzmann
2022-02-10 20:35 ` Helge Kreutzmann
2022-02-13 18:33   ` Mario Blättermann
2022-02-13 18:51     ` Helge Kreutzmann [this message]
2022-02-13 19:35       ` Bill Unruh
  -- strict thread matches above, loose matches on Subject: below --
2020-05-03 19:13 Helge Kreutzmann
2020-05-09 18:53 ` Michael Kerrisk
2020-05-09 19:00   ` Helge Kreutzmann
2020-05-09 19:05     ` Michael Kerrisk
2020-05-11  9:27       ` Karel Zak
2020-05-11  9:50         ` Helge Kreutzmann
2020-05-11 10:32         ` Michael Kerrisk (man-pages)

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=20220213185104.GA23259@Debian-50-lenny-64-minimal \
    --to=debian@helgefjell.de \
    --cc=mario.blaettermann@gmail.com \
    --cc=util-linux@vger.kernel.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.
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 NNTP newsgroup(s).