all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: emacs-devel@gnu.org
Subject: Bug report statistics on OS and arch
Date: Fri, 10 Mar 2017 19:44:22 -0500	[thread overview]
Message-ID: <8837ekprq1.fsf@fencepost.gnu.org> (raw)


Because it's Friday afternoon, some statistics from the Emacs bug database.
These don't represent anything other than who is making bug reports
(and including the template information), and are just for your amusement.
I haven't done anything fancy like include each distinct reporter email
address only once, so a particularly enthusiastic bug reporter could
skew the results. [1]

Based on the arch triplets (eg x86_64-unknown-linux-gnu) in the
"In GNU Emacs (xxx)" lines (11023 reports dating back 9 years):

5851 linux-gnu (53%)
3294 mingw     (30%)
1627 apple     (15%)
 111 cygwin     (1%)
  61 freebsd    (<1%)
  39 solaris
  22 netbsd
  10 openbsd
   4 aix
   2 hpux
   1 irix
   1 kfreebsd-gnu

5899 i?86     (54%)
4787 x86_64   (43%)
 174 powerpc   (2%)
  83 mips      (<1%)
  32 sparc
  31 amd64
  13 arm
   2 hppa
   1 ia64
   1 alpha

Based on the "System Distribution:" lines (2327 reports dating back 4.5 years):

866 Ubuntu   (37%)
691 Debian   (30%)
187 Fedora    (8%)
148 Arch      (6%)
104 SUSE      (4%)
 92 Gentoo    (4%)
 75 Mint      (3%)
 72 RHEL      (3%)
 26 Trisquel  (1%)
 24 gNewSense (1%)
  9 CentOS    (<1%)
  8 elementary OS
  4 Scientific Linux
  3 Devuan
  3 LMDE
  3 Raspbian
 11 Other, none with > 2


[1] If I tell you that one person is responsible for 10% of the 18500
Emacs bug reports over the past 9 years (next most enthusiastic is me
with 2%), you can see that this effect can be significant.



             reply	other threads:[~2017-03-11  0:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-11  0:44 Glenn Morris [this message]
2017-03-11 19:11 ` Bug report statistics on OS and arch Glenn Morris
2017-03-15  0:39   ` Glenn Morris

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=8837ekprq1.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=emacs-devel@gnu.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.