• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Creating new Xcode projects into Subversion (Was: Xcode and Subversion)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Creating new Xcode projects into Subversion (Was: Xcode and Subversion)


  • Subject: Re: Creating new Xcode projects into Subversion (Was: Xcode and Subversion)
  • From: Quincey Morris <email@hidden>
  • Date: Sat, 13 Jun 2009 17:51:23 -0700

On Jun 13, 2009, at 17:08, John Velman wrote:

Why is it a good idea to set up the project in a temporary place that will
be discarded?

Because the initial import (from the Repositories window) *clones* the imported folder into the repository. You need to check out another copy afterwards, because the checked out folder contains invisible .svn files with revision information for Xcode to use. The original folder doesn't have this information, so it's of no use any more.


Once you have the checked out folder, you can later add files to the repository from within Xcode itself (SCM->Add to Repository, as opposed to SCM->Repositories->Import). This *adopts* the added files into the repository, so you *don't* have to discard them and check out fresh copies.

Maybe one day the initial import will be smart enough to use "adopt" semantics instead of "clone" semantics, but until then there are these two ways of doing things.

If I set up as described by Jack Repenning (which sounds very good, and
I'll follow in the future), is it a good idea to keep the current working
version in the ~/src/Whatever directory, or discard this and check out a
new one every time I get back to working on the project?

Unless disk space or clutter is an issue, it seems unnecessary to discard the checked out version routinely. And possibly dangerous -- you'd be a bit annoyed if you threw away a checked out copy with uncommitted changes. (Keep in mind that Xcode is fairly, uh, cavalier about showing the correct modification status for files in its main window.)



_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >X-Code and Subversion (From: Clark Williams <email@hidden>)
 >Re: X-Code and Subversion (From: Jack Repenning <email@hidden>)
 >Re: Xcode and Subversion (From: Andrew Pontious <email@hidden>)
 >Creating new Xcode projects into Subversion (Was: Xcode and Subversion) (From: Jack Repenning <email@hidden>)
 >Re: Creating new Xcode projects into Subversion (Was: Xcode and Subversion) (From: John Velman <email@hidden>)

  • Prev by Date: Re: Creating new Xcode projects into Subversion (Was: Xcode and Subversion)
  • Next by Date: Re: Xcode as debugger only?
  • Previous by thread: Re: Creating new Xcode projects into Subversion (Was: Xcode and Subversion)
  • Next by thread: Re: Creating new Xcode projects into Subversion (Was: Xcode and Subversion)
  • Index(es):
    • Date
    • Thread