I am making a PHP tool that connects to a repository, downloads the list of commits and stores them locally. However, due to the possibility that certain repositories are HUGE and grabbing their log results in long waiting time and possible time-outs/errors, I would like to download each commit message using async requests.
So, I have a start and end points in revision history, and I can grab all logs like this:
svn log -r <from_revision>:<to_revision> <REPO_URL>
... and I will possibly end up with an XML file which is so huge that it will take long time to download, long time and lots of resources to parse, and long time to store.
If I know the start and the end point, I can create a for() loop to grab revisions one by one:
svn log -r <revision> ...
BUT, since I don't know which specific revisions exist for given path, I will receive an error. I can make the application to ignore that error during the update, but it's a nasty hack and it will post requests and wait for the responses anyway - which is not good at all.
So, I need something like this:
That way I would be able to make an array of valid revisions for the repository path and get them one by one.
All suggestions are welcome, thanks in advance.
"svn info --show-item revision" will give the current revision to which the current directory is updated.
Using the latest versions of Subclipse, you can actually view them without using the cmd prompt. On the file, simply right-click => Team => Switch to another branch/tag/revision.
As we described in the section called “Revisions”, revision numbers in Subversion are pretty straightforward—integers that keep getting larger as you commit more changes to your versioned data. Still, it doesn't take long before you can no longer remember exactly what happened in each and every revision.
I think your best bet would be to do the following svn log -l 100 0:{$newest} .\
that will retrieve the first 100 logs for a given directory or file. then read the last revision number returned, then request the next 100 svn log -l 100 {$last_ret_log}:{$newest} .\
that way you get 99 new log entries with each request but you wont get all of them.
If you have access to the repository tree on your Subversion server, then you can use svnlook history
to get a list of revision numbers.
More details can be found at http://svnbook.red-bean.com/en/1.1/re49.html.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With