unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Tassilo Horn <tassilo@member.fsf.org>
Cc: help-debbugs@gnu.org, emacs-devel@gnu.org
Subject: Re: Searching bugs before filing new ones
Date: Thu, 18 Nov 2010 03:19:26 -0500	[thread overview]
Message-ID: <rv62vvkprl.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <201011180848.18858.tassilo@member.fsf.org> (Tassilo Horn's message of "Thu\, 18 Nov 2010 08\:48\:18 +0100")


Cross-post and follow-up to help-debbugs.

Tassilo Horn wrote:

>> May I suggest searching for subject keywords before filing a bug?  Or
>> looking at the N newest bugs.
>
> Yes, you may, but as long as checking related/duplicate bugs is not a
> part of the usual bug filing procedure (aka M-x report-emacs-bug), it
> won't have an effect, I guess.

I thought it was basic courtesy to do a search before reporting a bug.
But this seems to have disappeared, along with "report your bug to the
right address", and "give a complete, self-contained description of
the problem".

> 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.

If you think that would be great, maybe you would like to write it.

> I don't know if debbugs has some interface for querying the database, or
> a better output format than the result html page.  But even that doesn't
> look awfully hard to parse to rip out the link to the bug and its
> subject...

Great, so it won't be long before someone writes this feature then.



  reply	other threads:[~2010-11-18  8:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20101117105947.GB21042@shi.workgroup>
     [not found] ` <E1PIgwj-0000gB-1H@fencepost.gnu.org>
     [not found]   ` <20101117163514.GA6164@shi.workgroup>
2010-11-17 19:28     ` bug#7419: 24.0.50; emacs -Q -nw positions cursor in empty lines on the second column 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           ` Glenn Morris [this message]
2010-11-18 10:14           ` Eli Zaretskii
2010-11-18 16:40             ` Andrew W. Nosenko
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=rv62vvkprl.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=help-debbugs@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).