Thanks, but no dice. And worse yet, I have the same problem with other files in the same and other projects.On Jan 12, 2013, at 12:37 AM, Quincey Morris < email@hidden> wrote: On Jan 11, 2013, at 20:19, Lorenzo Thurman <email@hidden> wrote:
Ok, it should be under version control, since I cloned the project from its repo. But I'll bite, so from the Command Line, I did a 'git add myfile.m' (that option is grayed out in Xcode). Now, I can commit the file from the CL. If I make a change to the same file and try to commit from Xcode again, I get the "...file is not under version control" error again. So now I go back to the CL, 'add' the file again, try to commit the file from Xcode and get the same error again, but, I can commit from the CL.
I had a very similar problem recently, and I could easily tell you how to fix it, except that I've utterly forgotten what I did. <sigh>
However, I'd suggest you try this voodoo approach, if you haven't already, and see if it helps:
-- Close the project or workspace in Xcode.
-- Go to the Repository tab of the organizer. Delete the repo entry that corresponds to your project. (Don't worry, this will be automatically recreated later.)
-- Go to the Projects tab of the organizer. Select your project and delete the derived data by clicking the button in the right pane. Once it's gone, your project should also disappear from the list on the left. (Don't worry, this will be automatically recreated later.)
-- Quit Xcode.
-- Go to the command line, and use git to make sure your file is added and the repo is committed.
-- Start Xcode and open your project or workspace.
I think there's a fair chance this will fix it.
"My Break-Dancing days are over, but there's always the Funky Chicken" --The Full Monty
Lorenzo Thurman
|