From: Juanma Barranquero <lekktu@gmail.com>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: Chong Yidong <cyd@stupidchicken.com>, emacs-devel@gnu.org
Subject: Re: How does the Emacs bug tracker work?
Date: Fri, 1 Jul 2011 13:08:35 +0200 [thread overview]
Message-ID: <BANLkTin=T576Amy2zvhWTndr0zQZAgnR2w@mail.gmail.com> (raw)
In-Reply-To: <87vcvm24ol.fsf@uwakimon.sk.tsukuba.ac.jp>
On Fri, Jul 1, 2011 at 03:03, Stephen J. Turnbull <stephen@xemacs.org> wrote:
> Actually, it can. The problem is that when you do a specific search
> for the-bug-you-are-about-to-report, most trackers will apply the "not
> closed" filter. In that case there will be a strong tendency to
> increase the number of dupes.
A strong tendency, with little impact IMHO because it seems that most
people does a very cursory "specific search for
the-bug-you-are-about-to-report". At least that's my feeling...
> Alternatively to all of the above, Roundup has a contributed script
> that regularly (by default, each week) sends a bug summary to the
> developers list. I don't know how many Emacs developers would use
> such a thing (it's a matter of taste, of course), but I know that
> several people on the python-dev list use theirs -- it's visible in
> their posts about "isn't it time to do something about this bug?" etc.
I would really like something that brought to attention stagnated bug reports.
Juanma
next prev parent reply other threads:[~2011-07-01 11:08 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 0:07 How does the Emacs bug tracker work? Lars Magne Ingebrigtsen
2011-06-30 0:32 ` Glenn Morris
2011-06-30 0:56 ` Lars Magne Ingebrigtsen
2011-06-30 5:00 ` Dan Nicolaescu
2011-06-30 9:09 ` Lars Magne Ingebrigtsen
2011-06-30 9:16 ` Julien Danjou
2011-06-30 9:32 ` Lars Magne Ingebrigtsen
2011-06-30 10:14 ` Bastien
2011-06-30 10:54 ` Julien Danjou
2011-06-30 9:39 ` Andreas Schwab
2011-06-30 9:40 ` Deniz Dogan
2011-06-30 13:04 ` Jason Rumney
2011-06-30 13:05 ` Deniz Dogan
2011-06-30 13:47 ` Juanma Barranquero
2011-06-30 14:35 ` Julien Danjou
2011-06-30 14:40 ` Juanma Barranquero
2011-06-30 14:44 ` Lars Magne Ingebrigtsen
2011-06-30 19:56 ` Stefan Monnier
2011-06-30 21:22 ` Lars Magne Ingebrigtsen
2011-07-01 2:25 ` Stefan Monnier
2011-07-01 10:00 ` Lars Magne Ingebrigtsen
2011-07-01 11:24 ` Michael Albinus
2011-07-01 15:24 ` Chong Yidong
2011-07-01 16:01 ` Drew Adams
2011-07-01 16:57 ` Lars Magne Ingebrigtsen
2011-07-01 17:16 ` Glenn Morris
2011-07-01 16:38 ` Michael Albinus
2011-07-01 0:18 ` Richard Stallman
2011-06-30 15:15 ` Chong Yidong
2011-06-30 16:30 ` Lars Magne Ingebrigtsen
2011-06-30 18:04 ` Glenn Morris
2011-06-30 20:54 ` Michael Albinus
2011-07-01 23:02 ` Glenn Morris
2011-07-02 11:23 ` Michael Albinus
2011-07-02 12:42 ` Lars Magne Ingebrigtsen
2011-07-02 12:57 ` Michael Albinus
2011-07-02 13:00 ` Lars Magne Ingebrigtsen
2011-07-02 13:21 ` Michael Albinus
2011-07-02 18:05 ` Glenn Morris
2011-07-02 20:04 ` Chong Yidong
2011-07-02 23:38 ` Michael Albinus
2011-07-02 18:03 ` Glenn Morris
2011-07-02 18:46 ` Michael Albinus
2011-07-02 20:19 ` Lars Magne Ingebrigtsen
2011-07-02 20:28 ` Michael Albinus
2011-07-02 22:25 ` Glenn Morris
2011-07-02 22:29 ` Lars Magne Ingebrigtsen
2011-07-02 22:42 ` Glenn Morris
2011-07-06 18:39 ` Lars Magne Ingebrigtsen
2011-07-06 20:05 ` Glenn Morris
2011-07-06 20:26 ` Lars Magne Ingebrigtsen
2011-07-01 6:55 ` Glenn Morris
2011-07-01 11:39 ` Richard Stallman
2011-06-30 16:32 ` Juanma Barranquero
2011-07-01 1:03 ` Stephen J. Turnbull
2011-07-01 11:08 ` Juanma Barranquero [this message]
2011-07-01 11:48 ` Lars Magne Ingebrigtsen
2011-07-01 12:18 ` Juanma Barranquero
2011-07-01 12:40 ` Lars Magne Ingebrigtsen
2011-07-01 12:51 ` Stephen J. Turnbull
2011-07-01 12:57 ` Juanma Barranquero
2011-07-01 13:02 ` Lars Magne Ingebrigtsen
2011-07-01 13:25 ` Michael Albinus
2011-07-01 15:27 ` Julien Danjou
2011-07-01 16:24 ` Lars Magne Ingebrigtsen
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='BANLkTin=T576Amy2zvhWTndr0zQZAgnR2w@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=stephen@xemacs.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.