> At 11:02 AM +1000 8/18/03, David Sitsky wrote:
> >Codestriker needs this information, to be able to link the file being
> >modified with the corresponding file in the repository, so that it can
> >retrieve the entire contents of this file, when displaying how the file
> >appears before any changes, and after.
>
> ... and that *is* available in .svn/*, e.g.
>
> > > svn info .bashrc
> >
> >Path: .bashrc
> >Name: .bashrc
> >Url: http://host/svn/jrepenning/trunk/home/.bashrc
>
> Indeed, it seems like his goal is "some incantation that lets him
> address the repository file in blissful disregard for all those messy
> working copy details," and that is just exactly what this URL is!
Yep, in my case, the URL is exactly what is required. In CVS diffs, the
RCS line provides similar information, it combines the path of the
repository plus the path of the file within the repository (ie, the
absolute path of the RCS file in the filesystem).
When a Codestriker topic is created, the repository that the code review
has been made against needs to be nominated, in this case, it would be
http://host/svn/jrepenning.
If the diff file contained in this instance,
http://host/svn/jrepenning/trunk/home/.bashrc in the Index: line, we could
determine what the file's relative path in the repository is. Then in the
main Codestriker GUI, the file's full contents could be retrieved directly
using svn commands, as all the information required to do this is
available (the revision number is also extracted).
This is how things work essentially when CVS diffs are parsed, the RCS line
is broken up into the CVSROOT, and the file's path within the repository.
--
Cheers,
David
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 19 02:46:50 2003