2013/3/6 Ronnie Ghose <[email protected]>: > ....... we can't just redirect to the head, which I assume does redirects > for all subpaths?
Github does not provide in-site redirects. In sourceforge we can put a redirect from /stable/old_module_name.html to /stable/new_module_name.html so that if someone has put a link in a blog post pointing to http://scikit-learn.org/stable/old_module_name.html , then anybody clicking on the link will get an HTTP 302 to the new address: http://scikit-learn.org/stable/new_module_name.html hence we can refactor the documentation structure without creating dead links on the rest of the Internet. If we switch the website hosting to github's gh-pages system we loose this feature that is provided by sourceforge (using .htaccess files that are not handled by github). -- Olivier http://twitter.com/ogrisel - http://github.com/ogrisel ------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev _______________________________________________ Scikit-learn-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
