From: Andy Wingo <wingo@pobox.com>
To: guile-devel <guile-devel@gnu.org>
Subject: who wrote the manual?
Date: Mon, 11 Oct 2010 21:39:55 +0200 [thread overview]
Message-ID: <m3mxqkecxg.fsf@unquote.localdomain> (raw)
Hi,
I was looking at the manual preface, and it says, quote:
The Guile reference and tutorial manuals were written and edited
largely by Mark Galassi and Jim Blandy. In particular, Jim wrote
the original tutorial on Guile's data representation and the C API
for accessing Guile objects.
But that sounds old. I cloned git://git.lwn.net/gitdm.git, and now we
see that:
~/src/guile$ git log -p -M doc | ../gitdm/gitdm -c /dev/null
Grabbing changesets...done
Processed 1515 csets from 26 developers
33 employers found
A total of 214004 lines added, 117077 removed (delta 96927)
[...]
Developers with the most changed lines
Neil Jerram 100687 (36.2%)
Marius Vollmer 38745 (13.9%)
Martin Grabmüller 16468 (5.9%)
Andy Wingo 13156 (4.7%)
Thien-Thi Nguyen 11676 (4.2%)
Kevin Ryde 10417 (3.7%)
Jim Blandy 8589 (3.1%)
Ludovic Courtes 7979 (2.9%)
Ludovic Courtès 4252 (1.5%)
Julian Graham 3129 (1.1%)
Rob Browning 2363 (0.8%)
Mikael Djurfeldt 1790 (0.6%)
Gary Houston 1605 (0.6%)
Michael Gran 1368 (0.5%)
Han-Wen Nienhuys 1221 (0.4%)
Brian Gough 1024 (0.4%)
Keisuke Nishida 603 (0.2%)
Andreas Rottmann 342 (0.1%)
Dirk Herrmann 247 (0.1%)
Ken Raeburn 50 (0.0%)
No Itisnt 42 (0.0%)
Stefan Jahn 27 (0.0%)
Daniel Kraft 17 (0.0%)
Greg J. Badros 10 (0.0%)
Jose A. Ortega Ruiz 8 (0.0%)
Michael Livshin 4 (0.0%)
Assuming that changed lines is the real measure of committing to the
manual, we can fairly say that Neil wrote the manual, with important
contributions from Marius on down. If we place the cutoff at 1% (and
that's totally arbitrary), we can mention 8 more names, which is plenty
for a preface, no?
But where is Mark Galassi in all of that, I wonder...
Andy
--
http://wingolog.org/
next reply other threads:[~2010-10-11 19:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 19:39 Andy Wingo [this message]
2010-10-11 20:16 ` who wrote the manual? Ludovic Courtès
2010-10-11 21:01 ` Andy Wingo
2010-10-12 9:45 ` Ludovic Courtès
2010-10-30 15:42 ` Neil Jerram
2010-10-11 20:27 ` Mike Gran
2010-10-11 21:30 ` Neil Jerram
2010-10-11 22:06 ` Andy Wingo
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3mxqkecxg.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-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.
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).