This is an automated email from git. It was generated because a ref
change was pushed to the "chrony/chrony.git" repository.
The annotated tag, 3.0-pre2 has been created
at 969cc37611ce8cc2ba03d33b33b9ef463d540a30 (tag)
tagging 16519ee2cc5eaed53c946b2a9cf3c56ad7df6be1 (commit)
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 16519ee2cc5eaed53c946b2a9cf3c56ad7df6be1 (commit)
via 50022e928644e3d727eaf8a7a8b334f3c998223c (commit)
via
> -Original Message-
> From: Miroslav Lichvar [mailto:mlich...@redhat.com]
> Sent: donderdag 15 december 2016 10:24
> To: chrony-dev@chrony.tuxfamily.org
> Subject: Re: [chrony-dev] Chrony 3.0-pre1 fails to send or receive data from
> socket on FreeBSD
>
> On Thu, Dec 15, 2016 at
On Thu, Dec 15, 2016 at 09:16:16AM +, Adri Koppes wrote:
> > Is it safe to assume this will be included in FreeBSD 11.1?
>
> This commit is not part of 11.0 release.
> The commit says 'MFC after 3 days', and has been done in 11-stable.
> 11-stable will eventually become 11.1, so I'm sure the
> -Original Message-
> From: Miroslav Lichvar [mailto:mlich...@redhat.com]
> Sent: woensdag 14 december 2016 17:07
> To: chrony-dev@chrony.tuxfamily.org
> Subject: Re: [chrony-dev] Chrony 3.0-pre1 fails to send or receive data from
> socket on FreeBSD
>
> On Wed, Dec 14, 2016 at
On Wed, Dec 14, 2016 at 10:34:19PM -0800, Denny Page wrote:
> Btw, it might be good for Chrony to support configuration for corrections
> similar to what is discussed in that thread:
>
> delayAsymmetry - corrects for any asymmetry between the Rx and Tx paths
> egressLatency - corrects the
