From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Bug report analysis
Date: 24 Nov 1996 09:44:03 +0100 [thread overview]
Message-ID: <m2682vubl8.fsf@proletcult.ifi.uio.no> (raw)
I had better things to do, so I decided to write a little snippet to
go through all the bug reports and generate an analysis. Kinda
interesting results -- you can clearly see the weeks I'm slacking off
and then deciding that I Have To Do Something.
It's too big to post here (well... 41k), but here's the URL:
<URL:http://www.ifi.uio.no/~larsi/gnus/bug-report>.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@ifi.uio.no * Lars Ingebrigtsen
next reply other threads:[~1996-11-24 8:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-11-24 8:44 Lars Magne Ingebrigtsen [this message]
1996-11-24 19:17 ` Hrvoje Niksic
1996-11-25 3:49 ` Lars Magne Ingebrigtsen
1996-11-25 16:47 ` Steven L Baur
1996-11-26 14:30 ` 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=m2682vubl8.fsf@proletcult.ifi.uio.no \
--to=larsi@ifi.uio.no \
/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).