From: Richard Stallman <rms@gnu.org>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: emacs-devel@gnu.org
Subject: Re: Bug statistics
Date: Sat, 26 Jun 2010 10:09:35 -0400 [thread overview]
Message-ID: <E1OSW4d-0002k1-9e@fencepost.gnu.org> (raw)
In-Reply-To: <87aaqjoe8b.fsf@uwakimon.sk.tsukuba.ac.jp> (stephen@xemacs.org)
> Amost 2000 bug reports not closed
> is rather disturbing.
Not really. That's 2000 (minor) contributions to be grateful for, and
2000 reasons for somebody new to volunteer to work on Emacs!
Unless they mostly came in in the last few weeks, it means
we are lagging in fixing the bugs after other people report them.
next prev parent reply other threads:[~2010-06-26 14:09 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 20:41 Bug statistics Glenn Morris
2010-06-23 21:48 ` Dan Nicolaescu
2010-06-23 23:46 ` Glenn Morris
2010-06-24 15:40 ` Richard Stallman
2010-06-24 17:59 ` Tassilo Horn
2010-06-25 10:24 ` Eli Zaretskii
2010-06-25 11:07 ` Tassilo Horn
2010-06-25 20:16 ` Chong Yidong
2010-06-26 0:48 ` Stephen J. Turnbull
2010-06-25 21:31 ` Karl Fogel
2010-06-26 8:53 ` Eli Zaretskii
2010-06-26 9:28 ` Tassilo Horn
2010-06-26 10:37 ` Eli Zaretskii
2010-06-26 19:38 ` Karl Fogel
2010-06-25 18:37 ` Richard Stallman
2010-06-26 1:18 ` Stephen J. Turnbull
2010-06-24 18:22 ` Karl Fogel
2010-06-24 18:34 ` Glenn Morris
2010-06-24 19:07 ` Karl Fogel
2010-06-24 19:21 ` Glenn Morris
2010-06-24 19:26 ` Karl Fogel
2010-06-25 1:28 ` Dan Nicolaescu
2010-06-25 1:40 ` Karl Fogel
2010-06-25 1:57 ` debbugs search output [was Re: Bug statistics] Glenn Morris
2010-06-25 2:03 ` debbugs search output Glenn Morris
2010-06-25 3:02 ` Karl Fogel
2010-07-03 13:19 ` Michael Albinus
2010-07-03 14:34 ` Chong Yidong
2010-07-03 18:36 ` Michael Albinus
2010-06-25 8:55 ` Bug statistics Yoni Rabkin
2010-06-25 10:27 ` Eli Zaretskii
2010-06-25 20:23 ` Chong Yidong
2010-06-26 8:55 ` Eli Zaretskii
2010-06-26 19:58 ` Chong Yidong
2010-06-26 14:09 ` Richard Stallman
2010-06-25 21:01 ` Dan Nicolaescu
2010-06-26 12:22 ` Eli Zaretskii
2010-06-26 14:14 ` Stephen J. Turnbull
2010-06-27 19:38 ` Eli Zaretskii
2010-06-27 20:25 ` Andreas Schwab
2010-06-24 18:26 ` Glenn Morris
2010-06-25 5:47 ` Stephen J. Turnbull
2010-06-26 14:09 ` Richard Stallman [this message]
2010-06-26 16:43 ` Stephen J. Turnbull
2010-06-27 21:09 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2019-10-20 19:32 Eli Zaretskii
2019-10-20 20:15 ` Lars Ingebrigtsen
2019-10-21 6:17 ` Eli Zaretskii
2019-10-21 7:24 ` Michael Albinus
2019-10-21 11:05 ` Lars Ingebrigtsen
2019-10-21 11:20 ` Eli Zaretskii
2019-10-21 12:26 ` Stefan Monnier
2019-10-21 13:04 ` Lars Ingebrigtsen
2019-10-21 13:50 ` Michael Albinus
2019-10-21 13:54 ` Lars Ingebrigtsen
2019-10-21 14:19 ` Michael Albinus
2019-10-21 14:32 ` Michael Albinus
2019-10-21 17:12 ` Lars Ingebrigtsen
2019-10-21 14:38 ` Lars 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
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=E1OSW4d-0002k1-9e@fencepost.gnu.org \
--to=rms@gnu.org \
--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 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).