public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Issue in man page adjtime.3
Date: Fri, 12 Jan 2024 00:02:45 +0100	[thread overview]
Message-ID: <ZaBzlVVjMx0DvATK@debian> (raw)
In-Reply-To: <ZaAiIziggN9w2Y_Q@meinfjell.helgefjelltest.de>

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

Hi Helge,

On Thu, Jan 11, 2024 at 05:15:15PM +0000, Helge Kreutzmann wrote:
> Hello Alejandro,
> Am Wed, Nov 01, 2023 at 05:17:42PM +0100 schrieb Alejandro Colomar:
> > On Wed, Nov 01, 2023 at 02:02:12PM +0000, Helge Kreutzmann wrote:
> > > Without further ado, the following was found:
> > > 
> > > Issue:    that can → that could
> > 
> > I'm not native, so I'll leave this one in case someone reading the list
> > wants to say something.
> > 
> > Thanks,
> > Alex
> > 
> > > 
> > > "The adjustment that B<adjtime>()  makes to the clock is carried out in such "
> > > "a manner that the clock is always monotonically increasing.  Using "
> > > "B<adjtime>()  to adjust the time prevents the problems that can be caused "
> > > "for certain applications (e.g., B<make>(1))  by abrupt positive or negative "
> > > "jumps in the system time."
> 
> Ok, then I mark this "WONTFIX" for now, so I don't report this again.

Re-reading it now, I think your report makes sense.  I'll fix it.

Have a lovely night,
Alex

-- 
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.

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

  reply	other threads:[~2024-01-11 23:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-01 14:02 Issue in man page adjtime.3 Helge Kreutzmann
2023-11-01 16:17 ` Alejandro Colomar
2024-01-11 17:15   ` Helge Kreutzmann
2024-01-11 23:02     ` Alejandro Colomar [this message]
2024-01-28 20:27       ` Alejandro Colomar

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=ZaBzlVVjMx0DvATK@debian \
    --to=alx@kernel.org \
    --cc=debian@helgefjell.de \
    --cc=linux-man@vger.kernel.org \
    --cc=mario.blaettermann@gmail.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