We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The "Why?" section, and others, of README.md (https://github.com/Moq/moq4/blob/029d510041c95714876bd1e43110af07c24f9aaa/README.md) point to blog articles at Clarius Consulting. None of the links resolve - all generate HTTP 503.
Also, the Internet Archive has nothing from those blogs, due to a robots.txt restriction.
The README set me up to want to read deeper into the issues motivating Moq.
Unless kzu will resurrect the blog / embed the posts in the repository how about the README not linking out to those pages?
The text was updated successfully, but these errors were encountered:
Fixed
Sorry, something went wrong.
Thank you @kzu ! I can read again. :)
thanks for reporting :)
On Thu, Oct 22, 2015 at 2:32 PM Nick Richards [email protected] wrote:
Thank you @kzu https://github.com/kzu ! I can read again. :) — Reply to this email directly or view it on GitHub #210 (comment).
Thank you @kzu https://github.com/kzu ! I can read again. :)
— Reply to this email directly or view it on GitHub #210 (comment).
No branches or pull requests
The "Why?" section, and others, of README.md (https://github.com/Moq/moq4/blob/029d510041c95714876bd1e43110af07c24f9aaa/README.md) point to blog articles at Clarius Consulting. None of the links resolve - all generate HTTP 503.
Also, the Internet Archive has nothing from those blogs, due to a robots.txt restriction.
The README set me up to want to read deeper into the issues motivating Moq.
Unless kzu will resurrect the blog / embed the posts in the repository how about the README not linking out to those pages?
The text was updated successfully, but these errors were encountered: