>> I don't see how this is going to work. The path is >> <repo>/top/branches/branchA/code/... >> but when I checkout, I checkout branchA. So my path, which may or may not >> start with branchA (depending how I checked out), will still not have the >> 'top/branches' part in it. And, of course, top/branches could be top/tags >> or it could be the trunk which is different again.
In the above example, you would set the repository path to be: <repo-path>/top/branches/branchA then when you do the diff, it will be the missing part. So basically, for each branch you need to review, and trunk, you need a separate repository object. I have to do this at work, and it works fine in practice. We use this and a mixture of post-commit scripts as well. Cheers, David ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Codestriker-user mailing list Codestriker-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/codestriker-user
