From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Angelo Graziosi Newsgroups: gmane.emacs.devel Subject: Re: Bootstrapping Emacs-23.0.60-trunk newly broken (GNU/Linux, Cygwin) Date: Sat, 12 Apr 2008 11:18:17 +0200 Message-ID: <48007E59.7040805@alice.it> References: <47FF2A29.4010908@alice.it> <4800687C.8090708@alice.it> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1207991960 14793 80.91.229.12 (12 Apr 2008 09:19:20 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 12 Apr 2008 09:19:20 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Apr 12 11:19:53 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 1Jkbto-0001ig-6X for ged-emacs-devel@m.gmane.org; Sat, 12 Apr 2008 11:19:52 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JkbtA-000156-67 for ged-emacs-devel@m.gmane.org; Sat, 12 Apr 2008 05:19:12 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Jkbt3-00013r-E7 for emacs-devel@gnu.org; Sat, 12 Apr 2008 05:19:05 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Jkbsw-0000vD-PJ for emacs-devel@gnu.org; Sat, 12 Apr 2008 05:19:03 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jkbsw-0000ut-DB for emacs-devel@gnu.org; Sat, 12 Apr 2008 05:18:58 -0400 Original-Received: from smtp-out112.alice.it ([85.37.17.112]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Jkbst-0003lK-7O; Sat, 12 Apr 2008 05:18:55 -0400 Original-Received: from FBCMMO03.fbc.local ([192.168.68.197]) by smtp-out112.alice.it with Microsoft SMTPSVC(6.0.3790.1830); Sat, 12 Apr 2008 11:18:51 +0200 Original-Received: from FBCMCL01B02.fbc.local ([192.168.69.83]) by FBCMMO03.fbc.local with Microsoft SMTPSVC(6.0.3790.1830); Sat, 12 Apr 2008 11:18:49 +0200 Original-Received: from [82.57.169.8] ([82.57.169.8]) by FBCMCL01B02.fbc.local with Microsoft SMTPSVC(6.0.3790.1830); Sat, 12 Apr 2008 11:18:49 +0200 User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) In-Reply-To: X-OriginalArrivalTime: 12 Apr 2008 09:18:49.0840 (UTC) FILETIME=[37F0CF00:01C89C7E] X-detected-kernel: by monty-python.gnu.org: Windows 2000 SP4, XP SP1+ 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:95025 Archived-At: Eli Zaretskii ha scritto: >> Date: Sat, 12 Apr 2008 09:45:00 +0200 >> From: Angelo Graziosi >> >> cd emacs >> ./configure >> make bootstrap >> >> >> Yes, it is heavy, but it is the only clean method that will guarantee >> the patches do no introduce regressions. > > Actually, there is no practical way to know for sure that changes > don't introduce regressions, in general. While "make bootstrap" will > make sure a bootstrap works on the submitter's machine (and is > recommended to those that can afford it), it says nothing about other > ways of building Emacs, nor about other machines and OSes we support. Obviously. But how could the trunk users to test a new patch if it breaks the bootstrap? 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. Sorry if I has been wrong. > So please calm down. The development trunk will inevitably become > broken from time to time, no matter what. If you must build the trunk > every day or even more frequently, and depend on the resulting binary > for your daily work, I suggest to make some arrangements to have the > previous working build available until you are sure the new one builds > and works successfully. I think that on my backup DVDs I have working build until two months ago. And if I build so often, it is to avoid the pile-up of bugs (when they are present) that would make hard to solve, mainly on Cygwin, on which no cygwin-guys take care of them. Sorry newly for the noise, Angelo.