linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jw schultz <jw@pegasys.ws>
To: linux-kernel@vger.kernel.org
Subject: Re: statistics for this mailinglist
Date: Mon, 24 Feb 2003 16:33:25 -0800	[thread overview]
Message-ID: <20030225003325.GA5283@pegasys.ws> (raw)
In-Reply-To: <20030224182742.GA2214@sgi.com>

On Mon, Feb 24, 2003 at 12:27:42PM -0600, Nathan Straz wrote:
> On Mon, Feb 24, 2003 at 07:09:25PM +0100, Maciej Soltysiak wrote:
> > > Top user-agents
> > > ----------------------------------------------------------
> > >  1]  207 Mutt/1.4i
> > >  2]   78 Mutt/1.3.28i
> > >  3]   70 Mutt/1.2.5.1i
> > >  4]   70 Mutt/1.5.3i
> > >  5]   60 ELM [version 2.5 PL6]
> > >  6]   55 Mulberry/2.2.1 (Linux/x86)
> > >  7]   51 Mutt/1.3.25i
> > >  8]   42 Sylpheed version 0.8.9 (GTK+ 1.2.10; i586-pc-linux-gnu)
> > >  9]   42 Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI)
> > > 10]   41 Ximian Evolution 1.2.1 (1.2.1-4)
> > No pine users? I'm shocked. So everybody uses mutt, eh? =:-)
> 
> I don't think Pine adds a user-agent header.  You could probably tell
> how many Pine users there are by checking by message ID.

And it wouldn't hurt to aggregate versions.  This is really
just a top-6 list.

 1]  476 Mutt (most common versions versions)
 2]   60 ELM [version 2.5 PL6]
 3]   55 Mulberry/2.2.1 (Linux/x86)
 4]   42 Sylpheed version 0.8.9 (GTK+ 1.2.10; i586-pc-linux-gnu)
 5]   42 Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI)
 6]   41 Ximian Evolution 1.2.1 (1.2.1-4)

Wonder where "unknown" would land if counted.

-- 
________________________________________________________________
	J.W. Schultz            Pegasystems Technologies
	email address:		jw@pegasys.ws

		Remember Cernan and Schmitt

  reply	other threads:[~2003-02-25  0:23 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-24 18:00 statistics for this mailinglist root
2003-02-24 18:09 ` Maciej Soltysiak
2003-02-24 18:22   ` Matti Aarnio
2003-02-24 18:27   ` Nathan Straz
2003-02-25  0:33     ` jw schultz [this message]
2003-02-25 19:02       ` Folkert van Heusden
2003-02-25 22:34         ` 'jw schultz'
2003-02-25  8:18     ` Jeandre du Toit
2003-02-24 18:41   ` Kenneth Johansson
2003-02-24 21:30   ` Rik van Riel
2003-02-25 19:00     ` Folkert van Heusden
2003-03-16  3:01 root
2003-03-30  2:01 root
2003-04-06  2:01 root
2003-04-13  2:01 root
2003-04-13 22:43 ` William Lee Irwin III
2003-04-14 13:50 ` Randy.Dunlap
2003-04-15 15:51   ` Robert Love
2003-04-15 19:41 Manfred Spraul
2003-04-15 21:11 ` John Bradford
2003-04-20  2:01 root
2003-04-20  2:04 ` William Lee Irwin III
2003-04-27  2:01 root
2003-04-27  2:24 ` Larry McVoy
2003-04-27  3:10   ` rmoser
2003-04-27  3:17     ` Larry McVoy
2003-04-27  2:30 ` Randy.Dunlap
2003-04-27  9:17 ` Jörn Engel
2003-04-27  7:47 Peter Kjellerstedt
2003-05-04  2:01 root
2003-05-04  7:43 ` William Lee Irwin III
2003-05-04  9:06   ` Jörn Engel
2003-05-04  9:10     ` William Lee Irwin III
2003-05-04  9:28       ` William Lee Irwin III
     [not found] <BKEGKPICNAKILKJKMHCACEFFCKAA.Riley@Williams.Name>
2003-05-04 21:03 ` Folkert van Heusden
2003-05-11  2:01 root
2003-05-11  9:03 ` Riley Williams
2003-05-11  9:07   ` Willy Tarreau
2003-05-18  2:01 root

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=20030225003325.GA5283@pegasys.ws \
    --to=jw@pegasys.ws \
    --cc=linux-kernel@vger.kernel.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.
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 NNTP newsgroup(s).