-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error 404 for new doc entries #581
Comments
I filed issues on these this morning. I will monitor the progress and update you here. |
https://clearlinux.org/features/telemetry is also dead |
@ghindman Please, foloow this link for telemetry info: |
Found that, yes, thanks - was just reporting the dead page. |
Thanks
From: Gavin Hindman <notifications@github.com>
Reply-To: clearlinux/clear-linux-documentation <reply@reply.github.com>
Date: Monday, July 8, 2019 at 10:03 AM
To: clearlinux/clear-linux-documentation <clear-linux-documentation@noreply.github.com>
Cc: "Palmeiro, Beatriz" <beatriz.palmeiro@intel.com>, Author <author@noreply.github.com>
Subject: Re: [clearlinux/clear-linux-documentation] Error 404 for new doc entries (#581)
Found that, yes, thanks - was just reporting the dead page.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#581?email_source=notifications&email_token=ABKWUWREWUNRG45QNHPZ3B3P6NXMNA5CNFSM4H4UMTE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZNXDPQ#issuecomment-509309374>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABKWUWXKYBCOAP5P5VSF5G3P6NXMNANCNFSM4H4UMTEQ>.
|
You may notice several You may receive a 404 because we have internally reorganized some sections. Thanks for your patience while we work out the kinks. :) |
Above two pages are now restored. Again, thanks for your patience as we work through this. |
Page not found for the links below:
https://clearlinux.org/documentation/clear-linux/guides/maintenance/cpu-performance
https://clearlinux.org/documentation/clear-linux/tutorials/tutorial-proxy
The text was updated successfully, but these errors were encountered: