The branch, change-clock-monotonic has been updated
discards 0f35b2dfd974ed85c8c08553c82ed8b5cd17ff75 (commit)
via a67176df59629c51e09c959908a068ed29c01b80 (commit)
This update added new revisions after undoing existing revisions. That is
to say, the old revision is not a strict subset of the new revision. This
situation occurs when you --force push a change and generate a repository
containing something like this:
* -- * -- B -- O -- O -- O (0f35b2dfd974ed85c8c08553c82ed8b5cd17ff75)
\
N -- N -- N (a67176df59629c51e09c959908a068ed29c01b80)
When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.
- Log -----------------------------------------------------------------
commit a67176df59629c51e09c959908a068ed29c01b80
Author: Gabriel Braga <gabriel.braga@xxxxxxxxxxxxx>
Date: Thu Apr 4 11:01:32 2024 +0200
Switch time() calls to monotonic clock calls (#7597)
In the event of a time warp the use of time() causes connections to
collapse.
This removes this problem by using a monotonic clock, based on libi2ncommon.
-----------------------------------------------------------------------
Summary of changes:
hooks/post-receive
--
C++ inter-process communication library
--
libt2n-git - see http://www.intra2net.com/en/developer/libt2n for details.
To unsubscribe send a mail to libt2n-git+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
