GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.

Commit edcbb1c1 authored 14 years ago by

John Koleszar

Browse files

Fix GF interval for non-lagged ARFs

When ARFs are enabled in non-lagged compress modes, the GF interval
was being reset to zero. Non-lagged ARF updates were enabled in commit
63ccfbd5, but this incorrect GF interval caused a quality regression.

Change-Id: I615c3b493f4ce2127044f4e68d0bcb07d6b730c3

parent 6d90f867

No related merge requests found

Hide whitespace changes

Inline Side-by-side

Showing with 3 additions and 2 deletions

Please register or to comment

Admin message

Fix GF interval for non-lagged ARFs