> That fixed the problem, but now I seem to have another problem I
> believe has to do with relative paths going 'up' in the folder tree. I
> have been able to reproduce it with the following repository:
> -a file that contains a script for checking in some files and
> the following does what I would expect it to do from within the root:
> TortoiseProc.exe /command:commit /path:"folder1*folder1/
> file1.txt*folder2*folder2/file2.txt" /logmsg:"msg"
> when i run the following from within the 'scripts' folder, i only get
> folder1 and file1.txt in my commit tialogue
> TortoiseProc.exe /command:commit /path:"../folder1*../folder1/
> file1.txt*../folder2*../folder2/file2.txt" /logmsg:"msg"
> I can work around it by changing the working directory to the top
> folder of my repository, but it would be nice to be able to use the
> same scripts I was using with the previous TortoiseSVN
Just tried this:
* created your suggested folder/file structure
* added it to a test repository
* checked it out again
* set a dummy property on all folders/files (so they
are all marked as 'modified'
* opened cmd.exe
* cd d:\test\testwc\scripts
* TortoiseProc.exe /command:commit
worked ok: all files and folders are shown in the commit dialog.
Are you sure that in your test case, folder2 and folder2/file2.txt are
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on 2008-08-18 17:56:04 CEST