From: "Andrew W. Nosenko" <andrew.w.nosenko@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Tassilo Horn <tassilo@member.fsf.org>, emacs-devel@gnu.org
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 [thread overview]
Message-ID: <AANLkTi=tO6Fj51hWfZ+zCr7UEtr48UM21tgJQvWP2vdy@mail.gmail.com> (raw)
In-Reply-To: <E1PJ1Vf-00019G-2J@fencepost.gnu.org>
On Thu, Nov 18, 2010 at 12:14, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Tassilo Horn <tassilo@member.fsf.org>
>> 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. Then 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.
--
Andrew W. Nosenko <andrew.w.nosenko@gmail.com>
next prev parent reply other threads:[~2010-11-18 16:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 10:59 bug#7419: 24.0.50; emacs -Q -nw positions cursor in empty lines on the second column Gregor Zattler
2010-11-17 12:17 ` Eli Zaretskii
2010-11-17 16:35 ` Gregor Zattler
2010-11-17 19:28 ` Eli Zaretskii
2010-11-17 19:41 ` Glenn Morris
2010-11-18 7:48 ` 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) Tassilo Horn
2010-11-18 8:19 ` Searching bugs before filing new ones Glenn Morris
2010-11-18 10:14 ` 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) Eli Zaretskii
2010-11-18 16:40 ` Andrew W. Nosenko [this message]
2010-11-18 18:19 ` Stephen J. Turnbull
2010-11-18 21:22 ` Searching bugs before filing new ones Glenn Morris
2010-11-18 22:20 ` Stefan Monnier
2010-11-19 11:51 ` tomas
2010-11-19 20:29 ` Glenn Morris
2010-11-21 20:10 ` tomas
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='AANLkTi=tO6Fj51hWfZ+zCr7UEtr48UM21tgJQvWP2vdy@mail.gmail.com' \
--to=andrew.w.nosenko@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=tassilo@member.fsf.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.