Open GoogleCodeExporter opened 8 years ago
What lock strategy are you using?
Original comment by daggett....@gmail.com
on 3 Nov 2011 at 5:29
It's the lockby property strategy. I had tried the newer strategy but it
didn't seem to work well, when we set up our PBSCC about 6 months ago.
Original comment by toff.til...@gmail.com
on 3 Nov 2011 at 5:37
"lock" strategy works fine.
it should work with new version of svn.
if you have troubles just ask questions or open an issue...
--
about "prop" strategy:
it uses file parsing of the .svn/entries file
it seems in the version 1.7 of svn the sqlite database used to store work copy
information...
development required...
Original comment by daggett....@gmail.com
on 3 Nov 2011 at 5:44
just an idea:
it should be possible to write sql that will retrieve data into same xml
structure as
returned by the command:
svn stat --xml --non-interactive --trust-server-cert -u -v "WORK_COPY_PATH"
in this case parser already written and minimum work is required in cpp code.
Original comment by daggett....@gmail.com
on 3 Nov 2011 at 7:05
Original issue reported on code.google.com by
toff.til...@gmail.com
on 2 Nov 2011 at 11:47