From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21220 invoked by alias); 25 May 2012 22:00:07 -0000 Received: (qmail 21146 invoked by uid 22791); 25 May 2012 22:00:06 -0000 X-SWARE-Spam-Status: No, hits=-6.3 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 25 May 2012 21:59:47 +0000 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q4PLxLPK003936 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 25 May 2012 17:59:21 -0400 Received: from psique (ovpn-113-148.phx2.redhat.com [10.3.113.148]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id q4PLxHeU015989; Fri, 25 May 2012 17:59:19 -0400 From: Sergio Durigan Junior To: Yao Qi Cc: Joel Brobecker , Mingjie Xing , Subject: Re: Gdb online docs error? References: <4FB6590A.6040704@codesourcery.com> <20120518165500.GQ29339@adacore.com> <4FBB1884.5090203@codesourcery.com> X-URL: http://www.redhat.com Date: Fri, 25 May 2012 22:00:00 -0000 In-Reply-To: <4FBB1884.5090203@codesourcery.com> (Yao Qi's message of "Tue, 22 May 2012 12:39:32 +0800") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2012-05/txt/msg00129.txt.bz2 On Tuesday, May 22 2012, Yao Qi wrote: > A lot users reference gdb html doc on sourceware.org, so it is not good > to give them a "page not found" error. I am happy to help on this, but > don't know what I can do. Same here. I can help if needed, I just found another page which is 404 on the server. -- Sergio