From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chad Brown Newsgroups: gmane.emacs.devel Subject: Re: HEAD broken for OSX- nsfsn.o fails to compile Date: Wed, 31 Mar 2010 15:56:21 -0700 Message-ID: <3291C5E1-3467-4028-AB3E-9BAE2A1CB970@mit.edu> References: <86y6h8uovh.fsf@red.stonehenge.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1270076210 19956 80.91.229.12 (31 Mar 2010 22:56:50 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 31 Mar 2010 22:56:50 +0000 (UTC) Cc: emacs-devel@gnu.org, "Randal L. Schwartz" To: Glenn Morris Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Apr 01 00:56:43 2010 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.69) (envelope-from ) id 1Nx6q0-0007Lf-Ba for ged-emacs-devel@m.gmane.org; Thu, 01 Apr 2010 00:56:40 +0200 Original-Received: from localhost ([127.0.0.1]:39529 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nx6pz-00087r-UC for ged-emacs-devel@m.gmane.org; Wed, 31 Mar 2010 18:56:39 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Nx6pv-00087k-0D for emacs-devel@gnu.org; Wed, 31 Mar 2010 18:56:35 -0400 Original-Received: from [140.186.70.92] (port=38905 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nx6ps-00085g-Mv for emacs-devel@gnu.org; Wed, 31 Mar 2010 18:56:34 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Nx6pr-0001Uf-Kn for emacs-devel@gnu.org; Wed, 31 Mar 2010 18:56:32 -0400 Original-Received: from dmz-mailsec-scanner-3.mit.edu ([18.9.25.14]:63012) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Nx6po-0001U3-Bl; Wed, 31 Mar 2010 18:56:28 -0400 X-AuditID: 1209190e-b7b82ae000005260-11-4bb3d31a8843 Original-Received: from mailhub-auth-4.mit.edu (MAILHUB-AUTH-4.MIT.EDU [18.7.62.39]) by dmz-mailsec-scanner-3.mit.edu (Symantec Brightmail Gateway) with SMTP id 7A.9A.21088.A13D3BB4; Wed, 31 Mar 2010 18:56:27 -0400 (EDT) Original-Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id o2VMuQdD023535; Wed, 31 Mar 2010 18:56:26 -0400 Original-Received: from [10.0.1.6] (c-98-247-149-76.hsd1.wa.comcast.net [98.247.149.76]) (authenticated bits=0) (User authenticated as yandros@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id o2VMuM91014621 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 31 Mar 2010 18:56:24 -0400 (EDT) In-Reply-To: X-Mailer: Apple Mail (2.1078) X-Brightmail-Tracker: AAAAAA== X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) 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:122995 Archived-At: On Mar 31, 2010, at 3:23 PM, Glenn Morris wrote: > Randal L. Schwartz wrote: >=20 >> Does this ring any bells? >=20 > Well, it rings these bells: >=20 > http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D5814 > http://lists.gnu.org/archive/html/emacs-devel/2010-03/msg01440.html >=20 > and the one from INSTALL.BZR: >=20 > Because the Bazaar version of Emacs is a work in progress, it will > sometimes fail to build. Please wait a day or so (and check the > bug and development mailing list archives) before reporting such > problems. In most cases, the problem is known about and is just > waiting for someone to fix it. You reply to the message wherein he points out that the breakage = happened 3 days ago with a quote suggesting he wait a day or so. He = checked the mailing list and saw that no one had mentioned it in well = more than ``a day or so'', and sent mail to the development list with = the specific breakage and changeset that caused it. =20 Complete Failure. I realize that it is very important to you that the bug tracker be used = appropriately, but this is not the first time I've seen you attempt to = hector people out of reporting development issues and asking development = questions on the development list -- not the bug tracker. While I'm = sure that you're doing good work, and I do appreciate those good works, = I do not consider this type of nanny-ism good, or desirable, and it = comes across to me as the opposite of helpful. Thanks, *Chad