> -----Original Message-----
> From: Troy Bull [mailto:troy.bull_at_gmail.com]
> Sent: Monday, February 25, 2008 1:49 PM
> To: users_at_subversion.tigris.org
> Subject: Best way to search across revisions
>
> Greetings
>
> I wanted to create a report for management on our Repository. I
> wanted to search each repository each revision for jar, ear, and war
> files. So, I stared by using
>
> svn ls -r # --verbose file://repo
>
> where # goes from 0 to the svnlook youngest for each repository
>
> This turns out to be VERY VERY slow, some of our repositories it was
> taking 90 minutes to complete a single revision.
>
> So, I decided to try something else.
>
> I did the following (in perl)
>
> open FL, "/usr/local/bin/svnadmin dump -r $rev --incremental $r
> 2>/dev/null |";
>
> where $rev is the revision and $r is the repository, then I filter the
> output for "files" and check them.
>
> Then I keep track of count of each type, size of each type, and user
> that is committing them into my Repository. This turned out the be
> WAY faster. and it appears to be working, I am on revision 2800 of
> 5500 on repository 56 of 209.
>
> Does anyone know of a better way to do this?
Instead of listing the full set of files for each and every revision
number (which is multiply redundant,) couldn't you just parse the output
of 'svn log -v' or 'svn log -v --xml' for complete list of jar/war/ear
files and what revisions they were added/modified in? (Ignore deletes.)
You would need a follow up command to get the file stats for each
file/rev pair.
Next question: what is the benefit of such a report? And is it worth
the time and labor to generate it?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-02-25 21:24:38 CET