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 11:30:07 +0300 Message-ID: References: <47FF2A29.4010908@alice.it> <4800687C.8090708@alice.it> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1207989096 7649 80.91.229.12 (12 Apr 2008 08:31:36 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 12 Apr 2008 08:31:36 +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 10:32:09 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 1Jkb9c-0003QY-N9 for ged-emacs-devel@m.gmane.org; Sat, 12 Apr 2008 10:32:08 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jkb8y-0006HL-7C for ged-emacs-devel@m.gmane.org; Sat, 12 Apr 2008 04:31:28 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Jkb8r-0006Ds-Ju for emacs-devel@gnu.org; Sat, 12 Apr 2008 04:31:22 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Jkb8p-00069e-IX for emacs-devel@gnu.org; Sat, 12 Apr 2008 04:31:20 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jkb8p-000697-DQ for emacs-devel@gnu.org; Sat, 12 Apr 2008 04:31:19 -0400 Original-Received: from mtaout6.012.net.il ([84.95.2.16]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Jkb8p-0002gL-7m for emacs-devel@gnu.org; Sat, 12 Apr 2008 04:31:19 -0400 Original-Received: from HOME-C4E4A596F7 ([80.230.158.193]) by i-mtaout6.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0JZ7002EXEXJM4J0@i-mtaout6.012.net.il> for emacs-devel@gnu.org; Sat, 12 Apr 2008 11:44:07 +0300 (IDT) In-reply-to: <4800687C.8090708@alice.it> X-012-Sender: halo1@inter.net.il X-detected-kernel: by monty-python.gnu.org: Solaris 10 (1203?) 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:95019 Archived-At: > 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. It also doesn't tell anything about run-time behavior, and as long as we don't have a test suite, there will always be a significant doubt. (Even when we do have a test suite, we cannot ask contributors to run it on more than one system -- her own.) IOW, I submit that asking people to be sure they don't cause regressions in these circumstances is tantamount to asking them not to commit changes at all. 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.