[chrony-dev] [GIT] chrony/chrony.git branch master updated. 4.2-pre1-3-g48bce35

[<git@xxxxxxxxxxxxx>]

This is an automated email from git. It was generated because a ref
change was pushed to the "chrony/chrony.git" repository.

The branch, master has been updated
       via  48bce351bfea7e4a0c3aa2012b5e64bc773494da (commit)
       via  25f93875d950334bc96020103efc828ec5a2ef6e (commit)
      from  ebc610fcb365dd0f62800ddbb9e1c4c9cc379a66 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 48bce351bfea7e4a0c3aa2012b5e64bc773494da
Author: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
Date:   Thu Dec 9 17:13:09 2021 +0100

    doc: describe use case for leapsecmode ignore option

commit 25f93875d950334bc96020103efc828ec5a2ef6e
Author: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
Date:   Thu Dec 9 13:27:50 2021 +0100

    doc: switch Solaris support to illumos
    
    For a long time, the Solaris support in chrony wasn't tested on a real
    Solaris system, but on illumos/OpenIndiana, which was forked from
    OpenSolaris when it was discontinued in 2010.
    
    While Solaris and illumos might have not diverged enough to make a
    difference for chrony, replace Solaris in the documentation with illumos
    to make it clear which system is actually supported by the chrony
    project.

-----------------------------------------------------------------------

Summary of changes:
 README               |  2 +-
 configure            |  2 +-
 doc/chrony.conf.adoc | 16 ++++++++++------
 doc/chronyd.adoc     |  8 ++++----
 sys_solaris.c        |  2 +-
 5 files changed, 17 insertions(+), 13 deletions(-)


hooks/post-receive
-- 
chrony/chrony.git

-- 
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.