[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Binary documentation in SVN?

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-02-15 22:13:27 CET

On Feb 15, 2005, at 3:00 PM, Nick Seigal wrote:
> I don't dispute that I guess, but all the tools can help by working
> together. The info I want is Subversion commit activity and would
> need to
> come from Subversion. This is not going to be found in email, IRC,
> etc.
> without some serious work and/or dedication to a process that captures
> all
> the commit info manually.

The entire open-source model is founded on this very idea -- suites of
tools working together to enable disparate collaboration.

   * a version control system that sends emails to the group when people
commit changes
   * a mailing list that enables developers to discuss and design
   * an IRC or IM system for real-time collaboration
   * a bugtracker that shows who is working on what, and when.
   * a place to share files and releases

This is how Sourceforge works. This is also the product that my own
company -- Collabnet -- sells to enormous customers. No tool exists in
a vacuum, doing everything by itself.

> Bugtrackers will show info on closed tickets and
> possibly progress towards closing, but not bytes-comitted or number of
> commits per day, etc. These metrics coulkd be very useful IMHO.

And you can do them all with Subversion. That's why every project
typically configures Subversion to send emails when people commit.
That's why the 'svn log' command exists. That's why the 'svn diff'
command exists. What other features do you need? I've not seen you
mention anything yet that people don't already do with Subversion.

>>> (That said, 'svn status -u' *will* show you which files have changed
>>> in the server, so you can predict merges and conflicts before you run
>>> 'svn update'.)
> Yes, and if it also showed *how often* the files had changed, *how
> much*,
> and *by whom* (i.e. commit-activity by user) that would be even
> better! ;-)

People have written such scripts. It's easy to do. Just parse 'svn
log' and 'svn diff' output from any client. Or write a post-commit
hook that does the same statistics gathering on the server-side.

(This seems like a very different problem that what you were asking
about originally...?)

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Feb 15 22:16:50 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.