Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. COMaybe I’m a little fuzzy on what you mean by getting Xcode to work with SVN 1.5 onwards, but my experience has been very smooth. SVN 1.6 comes prepackaged with Snow Leopard, and through the use of just two simple tutorials (http://www.rocxsoft.com/default.asp?W22 and http://iphonedevelopment.blogspot.com/2009/03/version-control-is-your-friend.html) SVN 1.6.2 is talking to Xcode 3.2.1 wonderfully on my machine. I’ve tackled the usual tasks just fine (import, export, commit, update, diff, etc.). It’s just the less common SVN tasks for which I’d like to find an Xcode-centric guide.
      singulars
    2. COI didn't realise that Snow Leopard comes with 1.6. That makes life much easier. If you're using Leopard then you're stuck with SVN 1.4, so then you need to install the OSX build of 10.6 from Collabnet and modify your PATH. To my knowledge, I don't think Xcode has much functionality beyond commit, diff, update, log, etc, and so for other operations such as branching and merging you're best off using a separate client. You can still use Xcode's SVN features while you're using another client, as long as both use the same underlying SVN version (eg SmartSVN 6 = svn 1.6)
      singulars
    3. COI haven't seen a specific usage guide for the SVN features of Xcode. I think the limited functionality that exists was sufficient for the Xcode devs to tick a box and say 'yes, it supports SVN/CVS/Perforce'. The functionality is so limited that I don't think there would be a dedicated guide for it (the best I've found is [here](http://developer.apple.com/tools/subversionxcode.html) ). I don't think the intention was for Xcode to be a fully-featured SCM client, rather just to support simple checkout/update/commit workflows.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload