RFC6330 Documentation (e1b41f22) · Commits · Anders Martinsson / libRaptorQ

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.

Verified Commit e1b41f22 authored Mar 03, 2018 by

Luker

Browse files

RFC6330 Documentation



update docs: a variable was renamed to keep the
C and C++ versions in sync

Signed-off-by: Luca Fulchir <luker@fenrirproject.org>

parent 74aa4e1c

Hide whitespace changes

Inline Side-by-side

Please register or to comment

Admin message

RFC6330 Documentation