From: Chad Brown <yandros@MIT.EDU>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org, "Randal L. Schwartz" <merlyn@stonehenge.com>
Subject: Re: HEAD broken for OSX- nsfsn.o fails to compile
Date: Wed, 31 Mar 2010 15:56:21 -0700 [thread overview]
Message-ID: <3291C5E1-3467-4028-AB3E-9BAE2A1CB970@mit.edu> (raw)
In-Reply-To: <mc634cjfkh.fsf@fencepost.gnu.org>
On Mar 31, 2010, at 3:23 PM, Glenn Morris wrote:
> Randal L. Schwartz wrote:
>
>> Does this ring any bells?
>
> Well, it rings these bells:
>
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=5814
> http://lists.gnu.org/archive/html/emacs-devel/2010-03/msg01440.html
>
> and the one from INSTALL.BZR:
>
> 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.
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
next prev parent reply other threads:[~2010-03-31 22:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 22:07 HEAD broken for OSX- nsfsn.o fails to compile Randal L. Schwartz
2010-03-31 22:18 ` Randal L. Schwartz
2010-03-31 22:23 ` Glenn Morris
2010-03-31 22:56 ` Chad Brown [this message]
2010-04-01 0:54 ` Chong Yidong
2010-04-01 6:10 ` Chad Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3291C5E1-3467-4028-AB3E-9BAE2A1CB970@mit.edu \
--to=yandros@mit.edu \
--cc=emacs-devel@gnu.org \
--cc=merlyn@stonehenge.com \
--cc=rgm@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.