From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Bootstrapping Emacs-23.0.60-trunk newly broken (GNU/Linux, Cygwin) Date: Sat, 12 Apr 2008 13:08:46 +0300 Message-ID: References: <47FF2A29.4010908@alice.it> <4800687C.8090708@alice.it> <48007E59.7040805@alice.it> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1207994984 22234 80.91.229.12 (12 Apr 2008 10:09:44 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 12 Apr 2008 10:09:44 +0000 (UTC) Cc: emacs-devel@gnu.org To: Angelo Graziosi Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Apr 12 12:10:16 2008 connect(): Connection refused Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JkcgY-0008C2-MQ for ged-emacs-devel@m.gmane.org; Sat, 12 Apr 2008 12:10:15 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jkcfu-0002pi-RH for ged-emacs-devel@m.gmane.org; Sat, 12 Apr 2008 06:09:34 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JkcfD-000267-UF for emacs-devel@gnu.org; Sat, 12 Apr 2008 06:08:51 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JkcfC-00024J-QU for emacs-devel@gnu.org; Sat, 12 Apr 2008 06:08:51 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JkcfC-000245-Lg for emacs-devel@gnu.org; Sat, 12 Apr 2008 06:08:50 -0400 Original-Received: from mtaout2.012.net.il ([84.95.2.4]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JkcfC-0004i0-M2 for emacs-devel@gnu.org; Sat, 12 Apr 2008 06:08:50 -0400 Original-Received: from HOME-C4E4A596F7 ([80.230.158.193]) by i_mtaout2.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0JZ700INOJHZ4O01@i_mtaout2.012.net.il> for emacs-devel@gnu.org; Sat, 12 Apr 2008 13:22:48 +0300 (IDT) In-reply-to: <48007E59.7040805@alice.it> X-012-Sender: halo1@inter.net.il X-detected-kernel: by monty-python.gnu.org: Solaris 9.1 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:95033 Archived-At: > Date: Sat, 12 Apr 2008 11:18:17 +0200 > From: Angelo Graziosi > CC: emacs-devel@gnu.org > > But how could the trunk users to test a new patch if it breaks the > bootstrap? If the changes also break a non-bootstrap build, then they can't, not until the trunk is fixed to build again. Or they can fix it themselves, if they have time and knowhow. > I thought that passing the bootstrap was the minimal request for > submitting a patch and that this would be reached if all start with the > same conditions in bootstrapping. I don't know if this is the minimal requirement, and it's not my place to introduce such requirements. All I can say is that bootstrapping takes a significant time, so requiring it from each submitter would be tough on them. FWIW, I bootstrap only very infrequently. > Sorry newly for the noise, No need to apologize. Thanks for timely reports of the breakage.