This is an automated email from git. It was enerated because a ref change was pushed to the repository "chrony/chrony.git".
The branch, master has been updated via c6245dc616574780bdf9134bd01d9a9a597c8fba (commit) via 4b36799ce1217c6c49945d822d33981c42fccda6 (commit) via d26bb9b4ebb63fd30dc680e055a3ca07012367a8 (commit) via 698404b02f98fa2a15541cc0dfe11049eabb55f7 (commit) via d46d7ad9479022a8f8ba278d1bcb98a7960798da (commit) via 7c6630905d2d00c31500eddde2142af24bf3bd33 (commit) via 129aa587c6e6ef902c4b2966115a48bdda0027b9 (commit) via cc1c6c94e32723aedf454cf48919e17b49c8741f (commit) from 41266cbaa09a7beae101c671bc97b52ee8c3673b (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 c6245dc616574780bdf9134bd01d9a9a597c8fba Author: Miroslav Lichvar <mlich...@redhat.com> List-Post: chrony-dev@chrony.tuxfamily.org Date: Mon Jun 30 17:30:17 2014 +0200 doc: update NEWS commit 4b36799ce1217c6c49945d822d33981c42fccda6 Author: Miroslav Lichvar <mlich...@redhat.com> List-Post: chrony-dev@chrony.tuxfamily.org Date: Mon Jun 30 17:20:06 2014 +0200 doc: update README commit d26bb9b4ebb63fd30dc680e055a3ca07012367a8 Author: Miroslav Lichvar <mlich...@redhat.com> List-Post: chrony-dev@chrony.tuxfamily.org Date: Mon Jun 30 17:19:40 2014 +0200 doc: update initstepslew description commit 698404b02f98fa2a15541cc0dfe11049eabb55f7 Author: Miroslav Lichvar <mlich...@redhat.com> List-Post: chrony-dev@chrony.tuxfamily.org Date: Mon Jun 30 16:21:42 2014 +0200 doc: update FAQ commit d46d7ad9479022a8f8ba278d1bcb98a7960798da Author: Miroslav Lichvar <mlich...@redhat.com> List-Post: chrony-dev@chrony.tuxfamily.org Date: Mon Jun 30 14:11:30 2014 +0200 Update configuration examples commit 7c6630905d2d00c31500eddde2142af24bf3bd33 Author: Miroslav Lichvar <mlich...@redhat.com> List-Post: chrony-dev@chrony.tuxfamily.org Date: Mon Jun 30 12:42:26 2014 +0200 sched: exit with fatal message when there is nothing to do With cmdport 0 and port 0, it's now possible that there is no descriptor watched or timer running, i.e. chronyd doing nothing and only waiting to be terminated. Replace the assertion with LOG_FATAL to exit properly. commit 129aa587c6e6ef902c4b2966115a48bdda0027b9 Author: Miroslav Lichvar <mlich...@redhat.com> List-Post: chrony-dev@chrony.tuxfamily.org Date: Mon Jun 30 12:36:52 2014 +0200 cmdmon: don't create socket when cmdport is 0 commit cc1c6c94e32723aedf454cf48919e17b49c8741f Author: Miroslav Lichvar <mlich...@redhat.com> List-Post: chrony-dev@chrony.tuxfamily.org Date: Fri Jun 27 17:26:54 2014 +0200 makefile: remove faq.php rule ----------------------------------------------------------------------- Summary of changes: Makefile.in | 4 - NEWS | 3 +- README | 4 +- chrony.conf.5.in | 9 +- chrony.texi.in | 237 ++++++++++++++++++++---------------------- cmdmon.c | 21 ++-- examples/chrony.conf.example | 3 + sched.c | 4 +- 8 files changed, 140 insertions(+), 145 deletions(-) hooks/post-receive -- chrony/chrony.git -- To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.