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

Scheduling an email of change logs.

From: Richard Quadling <rquadling_at_googlemail.com>
Date: Mon, 2 Nov 2009 13:32:50 +0000

Hi.

I'm a newbie to SVN, so please be gentle.

I'm on windows, so, please be even more gentle!

Using TortoiseSVN, I can manually create CSV files of the cache for
the repository (Right clicking a repository, choosing TortoiseSVN ->
Settings -> Cached Repositories -> Update & Export - more or less).

From there, I can create emails for each major project/branch per
day/week showing the commit messages and urls of changes.

Is there a way I can programmatically do the export? I want to have
the process run unattended, so no manual update & export.

As some indication of the project, there are 969 authors, 368,438
paths, 290144 revisions. It is a pretty big project.

I also see that I have a logcache folder containing a Repositories.dat
file and the cache file for the repository I'm interested in. Is this
file readable externally? Is the format/structure documented?

I've no problems accessing the CSV files to build my reports. I'd like
to be able to create the CSV files automatically or to update the
logcache file and access that.

Either way really.

Any help would be appreciated.

Regards,

Richard Quadling.

-- 
-----
Richard Quadling
"Standing on the shoulders of some very clever giants!"
EE : http://www.experts-exchange.com/M_248814.html
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
ZOPA : http://uk.zopa.com/member/RQuadling
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2413775
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-11-02 14:43:50 CET

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

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