From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: eshell-defgroup. Do we really need this? Date: Mon, 04 Aug 2008 11:34:49 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <86zlnszql2.fsf@lifelogs.com> References: <20080729222754.GC2208@muc.de> <86myjx3lt8.fsf@lifelogs.com> <48921019.6030308@gmail.com> <8663qk3g0w.fsf@lifelogs.com> <87y73giryj.fsf@elegiac.orebokech.com> <86iquk1nsk.fsf@lifelogs.com> <878wvgm4mw.fsf@uwakimon.sk.tsukuba.ac.jp> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1217867813 12125 80.91.229.12 (4 Aug 2008 16:36:53 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 4 Aug 2008 16:36:53 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Aug 04 18:37:44 2008 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 1KQ33w-0001RD-OY for ged-emacs-devel@m.gmane.org; Mon, 04 Aug 2008 18:37:37 +0200 Original-Received: from localhost ([127.0.0.1]:58670 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KQ331-00060a-HD for ged-emacs-devel@m.gmane.org; Mon, 04 Aug 2008 12:36:39 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KQ31X-0004xl-Lk for emacs-devel@gnu.org; Mon, 04 Aug 2008 12:35:07 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KQ31W-0004xB-Fa for emacs-devel@gnu.org; Mon, 04 Aug 2008 12:35:06 -0400 Original-Received: from [199.232.76.173] (port=43996 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KQ31W-0004x6-22 for emacs-devel@gnu.org; Mon, 04 Aug 2008 12:35:06 -0400 Original-Received: from main.gmane.org ([80.91.229.2]:57100 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KQ31V-0003G3-Lv for emacs-devel@gnu.org; Mon, 04 Aug 2008 12:35:06 -0400 Original-Received: from root by ciao.gmane.org with local (Exim 4.43) id 1KQ31S-00077V-K1 for emacs-devel@gnu.org; Mon, 04 Aug 2008 16:35:03 +0000 Original-Received: from 38.98.147.130 ([38.98.147.130]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 04 Aug 2008 16:35:02 +0000 Original-Received: from tzz by 38.98.147.130 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 04 Aug 2008 16:35:02 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 44 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 38.98.147.130 X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.60 (gnu/linux) Cancel-Lock: sha1:ttkRPW5gwDQQ5rCyjArXjetuu2I= X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) 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:102046 Archived-At: On Sat, 02 Aug 2008 13:18:15 +0900 "Stephen J. Turnbull" wrote: SJT> Ted Zlatanov writes: >> On Fri, 01 Aug 2008 19:08:04 +0200 Romain Francoise wrote: RF> My experience with running this buildbot (and others) suggests that RF> there is little value in doing this; buildbot does a clean build RF> every time so if it fails then we can be fairly sure that CVS is RF> broken. >> >> You think so even considering the large amount of people that would get >> this report? I'd rather be cautious and have at least one confirmation >> of the failure before reporting it. But, of course, it's your >> choice--as long as we report something. SJT> Romain's right, you don't need confirmation. If a clean build breaks, SJT> it's broke. What to do about it is another question. Builds can break for many reasons, some local (e.g. disk full). Why bother many people with a false report? It would condition them to ignore truly broken builds. That's my concern. SJT> XEmacs has a separate list for build reports, whether user-contributed SJT> or automatic. From Richard's comments about the BTS, I'd put money on SJT> him wanting a separate list for this, too. (That's 'cause I really SJT> like the odds, not because I speak for Richard.) Works for us. (We SJT> don't use buildbot, yet.) SJT> Python core just assumes that people (and in particular the release SJT> engineers) will be watching the buildbot's waterfall URL. Works for SJT> them. SJT> Python also has a system of "community" (ie, apps written in Python) SJT> buildbots with the intent of notifying somebody that the dev lines of SJT> Python are breaking stable builds. Current status is "failing SJT> miserably", as nobody pays attention to them. That is For reasons SJT> that I don't think apply to Emacs, but for the sake of completeness I SJT> include the case here. Thanks for explaining. I think the case for Emacs is simpler, but I am certainly not the one to make any decisions about it. I just want to provide the service because I want to do something about broken builds. Ted