From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Michael Albinus Newsgroups: gmane.emacs.devel Subject: Re: How does the Emacs bug tracker work? Date: Sat, 02 Jul 2011 13:23:59 +0200 Message-ID: <87r56953jk.fsf@gmx.de> References: <87zkkzfiz5.fsf@stupidchicken.com> <8762nnujk8.fsf@gmx.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1309605874 25125 80.91.229.12 (2 Jul 2011 11:24:34 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 2 Jul 2011 11:24:34 +0000 (UTC) Cc: emacs-devel@gnu.org To: Glenn Morris Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jul 02 13:24:30 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QcyJJ-0007Ix-EQ for ged-emacs-devel@m.gmane.org; Sat, 02 Jul 2011 13:24:29 +0200 Original-Received: from localhost ([::1]:56638 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QcyJH-00020h-WF for ged-emacs-devel@m.gmane.org; Sat, 02 Jul 2011 07:24:28 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:34853) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QcyJ1-00020M-H6 for emacs-devel@gnu.org; Sat, 02 Jul 2011 07:24:12 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QcyJ0-0007fY-4D for emacs-devel@gnu.org; Sat, 02 Jul 2011 07:24:11 -0400 Original-Received: from mailout-de.gmx.net ([213.165.64.23]:36871) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1QcyIz-0007eW-CG for emacs-devel@gnu.org; Sat, 02 Jul 2011 07:24:09 -0400 Original-Received: (qmail invoked by alias); 02 Jul 2011 11:24:00 -0000 Original-Received: from p57BB8C08.dip0.t-ipconnect.de (EHLO detlef.gmx.de) [87.187.140.8] by mail.gmx.net (mp025) with SMTP; 02 Jul 2011 13:24:00 +0200 X-Authenticated: #3708877 X-Provags-ID: V01U2FsdGVkX18LGE4T78ULxHPIKw64c8CF3a8G3dMVcrCOXxI96J gPZryjD4WHt0O5 In-Reply-To: (Glenn Morris's message of "Fri, 01 Jul 2011 19:02:50 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-Y-GMX-Trusted: 0 X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 213.165.64.23 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:141427 Archived-At: Glenn Morris writes: Hi Glenn, >> debbugs.el does not suffer from this limitation: >> >> (length (debbugs-get-bugs :severity "normal")) >> => 1860 > > It does, however, have pretty much the same impact on the server, in > terms of using quite a lot of memory, which is why I put the 400 bugs > limitation into the web-based search. So I think this could cause > problems if a lot of people start using it. What does cause the load? debbugs-get-bugs or debbugs-get-status? I suspect the latter one, which could carry an arbitrary number of bugnumbers. > Could you consider putting in a similar kind of limit to the > number of bugs the `debbugs-emacs' command will fetch? I believe, this shall be implemented in the frontend Lars is working on. debbugs-get-bugs returns the bug numbers, and before calling debbugs-get-status, the frontend could ask (like in gnus): How many articles from gmane.emacs.devel (available 140599, default 200): Btw, for debian.org such a restriction would be even more important: (let ((debbugs-port "debian.org")) (debbugs-newest-bugs 1)) => (632453) Best regards, Michael.