From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Andrew W. Nosenko" Newsgroups: gmane.emacs.devel Subject: Re: Searching bugs before filing new ones (was: Re: bug#7419: 24.0.50; emacs -Q -nw positions cursor in empty lines on the second column) Date: Thu, 18 Nov 2010 18:40:07 +0200 Message-ID: References: <20101117105947.GB21042@shi.workgroup> <8362vvda2j.fsf@gnu.org> <201011180848.18858.tassilo@member.fsf.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1290098421 17881 80.91.229.12 (18 Nov 2010 16:40:21 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 18 Nov 2010 16:40:21 +0000 (UTC) Cc: Tassilo Horn , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 18 17:40:17 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 1PJ7Wx-0003gN-Js for ged-emacs-devel@m.gmane.org; Thu, 18 Nov 2010 17:40:15 +0100 Original-Received: from localhost ([127.0.0.1]:60514 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PJ7Wx-00057J-1m for ged-emacs-devel@m.gmane.org; Thu, 18 Nov 2010 11:40:15 -0500 Original-Received: from [140.186.70.92] (port=45485 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PJ7Ws-000575-Gk for emacs-devel@gnu.org; Thu, 18 Nov 2010 11:40:11 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PJ7Wq-0000K5-FD for emacs-devel@gnu.org; Thu, 18 Nov 2010 11:40:10 -0500 Original-Received: from mail-qw0-f41.google.com ([209.85.216.41]:51226) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PJ7Wq-0000Jo-D1; Thu, 18 Nov 2010 11:40:08 -0500 Original-Received: by qwb8 with SMTP id 8so102865qwb.0 for ; Thu, 18 Nov 2010 08:40:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Q8uQxxwZRTVEzaxDuBO8wfoAF5TcPviptmqgOPRykoI=; b=osalcpXFiVO/AnSDUrLnDt62Rirsczcc+uH5KxUa2Omlq7kyJiV0ZNWh8r6Po2yUWH jTwuRwMguQCAI02tHM7EAv3TEb0x9DowqV+v4a1N0z2FEkU/Y6iRinu3KbPA1Z8HTL63 l/LmQXHnuUIvhC2Jgt+vmFe/C3OBxogC0BafY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=FbsK1OxrDJVjhobYaGikCe9I97ot+e+aPQQbX1hfu7M2iKn0GU1DImbWrZxiIAydhh QNEUp0yX5pTN9MCVNjat94RhSBoXk1mjRXVsxdJE5lvtRoNWTNd9HbVNlgTO/uOU3VgK b7t+UHb1nY0FlKQdWcigSB4JPotc//Ngft5l8= Original-Received: by 10.229.251.204 with SMTP id mt12mr732430qcb.182.1290098407304; Thu, 18 Nov 2010 08:40:07 -0800 (PST) Original-Received: by 10.229.95.209 with HTTP; Thu, 18 Nov 2010 08:40:07 -0800 (PST) In-Reply-To: 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:132819 Archived-At: On Thu, Nov 18, 2010 at 12:14, Eli Zaretskii wrote: >> From: Tassilo Horn >> Date: Thu, 18 Nov 2010 08:48:18 +0100 >> >> It would be great if M-x report-emacs-bug would query for "Bug keywords" >> first (e.g., tty cursor column), then somehow query the bug database and >> show a buffer with possibly related bug subjects including links to the >> bugtracker. =A0Then a user should be able to either say "nope, I have a >> different bug" and file a new one, or attach to one of the listed bugs. > > Yes, it would be nice to have such a feature. Usually, in general case, an user that reports a bug has not enough skills and knowledge in the area for be sure that a bug, which he going to report, and a bug, which found by pre-submit query, are duplicates indeed. Therefore, request he to make such decition is just unfair (and ineffective). If finding of potencial duplicates may be automated indeed, then I would to create crontab job (for example) with this automated searching and then publish the report somewhere (through www or e-mail, for example) for following review by people with appropriate knowledge. --=20 Andrew W. Nosenko