• 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: Is XCode 3 SCM more dysfunctional than ever or am I doing something wrong?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Is XCode 3 SCM more dysfunctional than ever or am I doing something wrong?


  • Subject: Re: Is XCode 3 SCM more dysfunctional than ever or am I doing something wrong?
  • From: David Dunham <email@hidden>
  • Date: Sun, 25 Nov 2007 13:02:27 -0800


On 25 Nov 2007, at 12:44, Jeff DuMonthier wrote:

What is the project root? (You never needed to set this before.) In the past, Xcode was happy using its anemic SCM abilities on any file that was in the project. Now it seems to exuberantly -- but exclusively -- offer its helpful abilities on ALL files in the project root.

I'm not entirely sure what a project root is (unless it is the folder containing the project, which is the root of my hierarchy) but I think this is what I am seeing. Files that come as part of the hierarchy with the project from the same repository (i.e. the hierarchy in the working directory matches the repository) get handled. Files that come from other repositories (or possible from other points in the hierarchy from the project repository) only get handled on a per file basis when you manually force XCode to do so. Otherwise they are ignored for SCM.

You may want to set a higher project root then. It's in the General tab of Project Info.


For many of us, this is not what we want, as the root is so bushy as to slow things down. Except that without being rooted in the root, a file can't be SCMed.

Which is pretty much useless unless your entire code base is a contiguous subset of the hierarchy of one repository. I have a separate repository for projects and project specific files, a separate repository for common utility code and another for more specialized modules that still may be shared among multiple projects.

You probably need to file a bug then. (Our case is a single repository, but Xcode's new behavior is still problematic.)


David Dunham     A Sharp, LLC
Voice/Fax: 206 783 7404     http://a-sharp.com
Efficiency is intelligent laziness.

_______________________________________________
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


  • Follow-Ups:
    • Re: Is XCode 3 SCM more dysfunctional than ever or am I doing something wrong?
      • From: Jeff DuMonthier <email@hidden>
References: 
 >Is XCode 3 SCM more dysfunctional than ever or am I doing something wrong? (From: Jeff DuMonthier <email@hidden>)
 >Re: Is XCode 3 SCM more dysfunctional than ever or am I doing something wrong? (From: David Dunham <email@hidden>)
 >Re: Is XCode 3 SCM more dysfunctional than ever or am I doing something wrong? (From: Jeff DuMonthier <email@hidden>)

  • Prev by Date: Re: Is XCode 3 SCM more dysfunctional than ever or am I doing something wrong?
  • Next by Date: Re: XCode 3.0 header/scope/namespace issues?
  • Previous by thread: Re: Is XCode 3 SCM more dysfunctional than ever or am I doing something wrong?
  • Next by thread: Re: Is XCode 3 SCM more dysfunctional than ever or am I doing something wrong?
  • Index(es):
    • Date
    • Thread