Re: Another subversion dilemma
Re: Another subversion dilemma
- Subject: Re: Another subversion dilemma
- From: Scott Cherf <email@hidden>
- Date: Mon, 21 Jun 2010 16:23:38 -0700
On Jun 21, 2010, at 3:34 PM, Matthew Weinstein wrote:
> It is the XCode angle that has me troubled. In the past if I've tried to do anything in my working directory not done by XCode XCode will then cease committing things, and give all sorts of errors
Matthew -
It's difficult to say for sure, but it sounds as if you've tried deleting a directory under SVN control then copying files from another place into your Xcode workspace expecting that the changes will then be picked up and an Xcode commit will send the modified files off to the SourceForge repository, yes?
If so, your problem is that when you delete the working directory (the one Xcode is using) you also delete all the SVN control files that are in the directory (you'll find them under '.svn' in each directory that's under SVN control). Deleting those directories is very bad and will hose up SVN in ways that are to horrible to describe; blood will begin flowing freely from every pore of your body, the sky will open and rain nasty stuff on you and all your descendants. Life will never be the same.
You'll need to individually replace the files you've changed by copying them, use 'svn add' or 'svn delete' to adjust the repository for any files you've added and deleted, etc.
This isn't exactly an Xcode topic. Had you performed all of the changes in Xcode then you would have not had the difficulties you're having. Because you're doing it manually you'll need to read up on SVN. There's a manual available on the web that's free, Google it.
Scott.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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