-
Notifications
You must be signed in to change notification settings - Fork 4
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
Missing links #29
Comments
Nice catch. As stated previously, this is still under development. If you have a few minutes to create a fork and pull request, that would be awesome! Thanks, Clint |
I've edited the name of this issue to track all missing links. I'm using this link to validate them. |
First batch of links from page: http://gooseproject.org/ |
Second batch of links from page: http://gooseproject.org/2011/10/22/watching-a-goose-run.html
|
Third batch of links from page: http://gooseproject.org/community.html All from above plus:
|
Forth batch of links from page: http://gooseproject.org/download.html most of first batch as well as: |
from: http://gooseproject.org/signup.html just the above |
from: http://gooseproject.org/2011/11/07/weekly-meetings.html
|
Update tools includes to work towards #29 getting fixed.
Gosh! I go away for a few days, and all this work gets done! Is there anything else outstanding that I can help with? I'm still getting to grips with this CVS system, will I need to wait for the 'pull request' to get merged os that I don't overwrite changes? Basically, I'm not 100% sure which branch to get! |
Mister, I think your pull request was already merged. You should see an email to that effect from github recently. As for which branch to get, you use master in your fork, and make pull requests against the main master in the gooseproject. Hope that helps. |
These links are referenced, and the pages don't exist in the website structure.
The text was updated successfully, but these errors were encountered: