From: Eric McDonald <mcdonald@phy.cmich.edu>
To: cstevens@gencom.us
Cc: Xconq Mailing List <xconq7@sources.redhat.com>
Subject: Re: CVS Monitor Online
Date: Wed, 29 Sep 2004 01:45:00 -0000 [thread overview]
Message-ID: <415A11F5.201@phy.cmich.edu> (raw)
In-Reply-To: <1096349979.6661.0.camel@localhost>
D. Cooper Stevenson wrote:
> http://www.xconq.org/cvsmonitor
Decent. But I notice that the top-level files don't show up.
Eric
General P.S to no one in particular:
The CVS commit activity (Activity by Author) summaries at:
http://www.xconq.org/cvsmonitor?repository=Xconq_CVS&cmd=viewBrowseRepository
are quite interesting, though pretty much as I expected. I am not going
to try to imply anything in the way of metrics, but 3 of the 4 top CVS
committers have similar add:remove and add:change ratios; the other one
doesn't. I had suspected this picture from mailing list and changelog
evidence, but to see it quantified solidifies it as fact....
next prev parent reply other threads:[~2004-09-29 1:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 13:44 D. Cooper Stevenson
2004-09-29 1:45 ` Eric McDonald [this message]
2004-09-29 2:18 ` D. Cooper Stevenson
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=415A11F5.201@phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=cstevens@gencom.us \
--cc=xconq7@sources.redhat.com \
/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).