> On Thu, 9 Jul 2020, Richard Sandiford wrote:
> >> I'm trying Tree Browser during debugging, but failed.
> >> I found that tree-browser.c and tree-browser.def have been removed at
> >> 2015-07-25. So, to avoid misunderstanding, can we remove this
> >> tree-browser page too?
> > Thanks for the patch.  Seems like a good idea to me.  I guess the only
> > question is whether we should keep it around for historical purposes,
> > but with a big banner to say that it's no longer up-to-date.  I also
> > don't know whether we try to avoid 404s on old pages.
> 
> Thank you, Hujp and Richard!
> 
> We generally try to avoid 404s.  So in case we remove a page put in a 
> redirect.
> You can do so via a new entry in wwwdocs/htdocs/.htaccess (which I believe is
> self explanatory, and I'm happy to help, too).
> 
Thank you, Richard and Gerald!

Since the tree-ssa/index.html and tree-ssa/tree_browser.html are no longer
up-to-date, I think it may be better to add a redirect than to update.
Is there a page means the page which was redirected is no longer up-to-date?
Or just redirect to index.html itself as the following, it's OK?

Regards.
Hujp

---
diff --git a/htdocs/.htaccess b/htdocs/.htaccess
index 18997d63..67ee474f 100644
--- a/htdocs/.htaccess
+++ b/htdocs/.htaccess
@@ -67,6 +67,7 @@ Redirect permanent /proj-optimize.html                
https://gcc.gnu.org/projects/optimize.ht
 Redirect permanent /projects.html              https://gcc.gnu.org/projects/
 Redirect permanent /projects/cxx1z.html                
https://gcc.gnu.org/projects/cxx-status.html#cxx1z
 Redirect permanent /projects/web.html          https://gcc.gnu.org/about.html
+Redirect permanent /projects/tree-ssa/tree-browser.html        
https://gcc.gnu.org/projects/tree-ssa/
 Redirect permanent /reghunt-howto.html         
https://gcc.gnu.org/bugs/reghunt.html
 Redirect permanent /svn.html                   https://gcc.gnu.org/git.html
 Redirect permanent /svnwrite.html              
https://gcc.gnu.org/gitwrite.html
--

> My recommendation in a case like this is to follow the approach of adding a 
> big
> banner at the top as you suggest, Richard. That said, if the consensus by
> you/those working in this area is to completely remove the page, that is
> perfectly fine, too.
> 
> Gerald
> 



Reply via email to