From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Bootstrapping Emacs-23.0.60-trunk newly broken (GNU/Linux, Cygwin) Date: Sat, 12 Apr 2008 09:45:34 -0400 Message-ID: References: <47FF2A29.4010908@alice.it> <4800687C.8090708@alice.it> <48007E59.7040805@alice.it> <87d4ovl2id.fsf@elegiac.orebokech.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1208007957 23675 80.91.229.12 (12 Apr 2008 13:45:57 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 12 Apr 2008 13:45:57 +0000 (UTC) Cc: Eli Zaretskii , emacs-devel@gnu.org, Angelo Graziosi To: "Juanma Barranquero" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Apr 12 15:46:30 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 1Jkg3m-0002rG-94 for ged-emacs-devel@m.gmane.org; Sat, 12 Apr 2008 15:46:26 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jkg38-0000AI-Cf for ged-emacs-devel@m.gmane.org; Sat, 12 Apr 2008 09:45:46 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Jkg33-0000AB-Pj for emacs-devel@gnu.org; Sat, 12 Apr 2008 09:45:41 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Jkg33-00009Z-5f for emacs-devel@gnu.org; Sat, 12 Apr 2008 09:45:41 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jkg33-00009W-0M for emacs-devel@gnu.org; Sat, 12 Apr 2008 09:45:41 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Jkg2x-0008Cz-Rn; Sat, 12 Apr 2008 09:45:35 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhQFACNaAEjO+KV8/2dsb2JhbACBXakG X-IronPort-AV: E=Sophos;i="4.25,646,1199682000"; d="scan'208";a="18383338" Original-Received: from smtp.pppoe.ca (HELO smtp.teksavvy.com) ([65.39.196.238]) by ironport2-out.teksavvy.com with ESMTP; 12 Apr 2008 09:45:34 -0400 Original-Received: from pastel.home ([206.248.165.124]) by smtp.teksavvy.com (Internet Mail Server v1.0) with ESMTP id SRF64534; Sat, 12 Apr 2008 09:45:34 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 634FC8C11; Sat, 12 Apr 2008 09:45:34 -0400 (EDT) In-Reply-To: <87d4ovl2id.fsf@elegiac.orebokech.com> (Romain Francoise's message of "Sat, 12 Apr 2008 13:46:18 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Genre and OS details not recognized. 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:95050 Archived-At: >> In an ideal world, it'd be nice if each change were to be known >> not to break bootstrapping. But the fact is, most patches do not >> break it [1], and the ones that do are usually detected quite >> fast, so it is a waste of resources to require everyone to >> bootstrap before each commit [2]. > While that is certainly true, it's also a waste of time for our > users to have to report bugs that could be avoided, and a waste of > our own time because we have to handle the reports. The problem is that users are not supposed to just come and whine about bootstrap failures. They should at least do the work of figuring out either a patch to fix it, or to find out the commit that broke it, ... This is a development branch: expect it to be broken, Stefan PS: The only problem that I would consider as really serious, even for the development branch is a bug that risks losing data.