• 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: The One True Stage Re: Xcode - AN APPLE OPPORTUNITY!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: The One True Stage Re: Xcode - AN APPLE OPPORTUNITY!


  • Subject: Re: The One True Stage Re: Xcode - AN APPLE OPPORTUNITY!
  • From: Roland King <email@hidden>
  • Date: Sun, 04 Mar 2012 13:03:37 +0800

On Mar 4, 2012, at 12:57 PM, Matt Neuburg wrote:

>
> On Mar 3, 2012, at 8:44 PM, Fritz Anderson wrote:
>
>> That's not the One True Model you have in mind,* but you do, in fact, "get to decide what gets ... to go into the next commit."
>>
>> * (And I could introduce you to someone whose One True Model derives from Subversion. Duke it out amongst yourselves until you come up with a UI that fits both.)
>>
>
> When I was using SVN, I ignored Xcode's version control features and used the command line. That's what I'd like to do with git as well, but Xcode is more proactive as regards git (perhaps because "add" means something very different in git than it does in SVN) so I must struggle against it. It's not fatal, but it is inconvenient, since, as Stefan said, I do end up quitting Xcode often to do a little git management. So, to sum up, I don't have in mind any One True Model. I would just like an option for no model at all. An *option*, mind you. I'm not saying what Xcode is doing is bad, I just think it would be even *better* if there were an *option* to turn it off. That seems a harmless and positive suggestion, and easily implemented - hardly a fit object of vitriol. m.

In what cases have you found it necessary to quit Xcode to run git from the command line? I've found it very tolerant of me making wholesale changes, including backing up to a previous revision with radically different files, on the command line and having Xcode just pick up and continue from where I end up. The only operation I've found flaky is merging back a branch which often results in all my targets being destroyed. I saw a comment about that on the developer forums too, so it's not just me.

Just interested in what situations Xcode falls over when git is messed about with behind the scenes, I've not found one.
 _______________________________________________
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: The One True Stage Re: Xcode - AN APPLE OPPORTUNITY!
      • From: Matt Neuburg <email@hidden>
    • Re: The One True Stage Re: Xcode - AN APPLE OPPORTUNITY!
      • From: Luther Baker <email@hidden>
References: 
 >Re: Xcode - AN APPLE OPPORTUNITY! (From: Matt Neuburg <email@hidden>)
 >The One True Stage Re: Xcode - AN APPLE OPPORTUNITY! (From: Fritz Anderson <email@hidden>)
 >Re: The One True Stage Re: Xcode - AN APPLE OPPORTUNITY! (From: Matt Neuburg <email@hidden>)

  • Prev by Date: Re: The One True Stage Re: Xcode - AN APPLE OPPORTUNITY!
  • Next by Date: Re: Xcode-users Digest, Vol 9, Issue 100
  • Previous by thread: Re: The One True Stage Re: Xcode - AN APPLE OPPORTUNITY!
  • Next by thread: Re: The One True Stage Re: Xcode - AN APPLE OPPORTUNITY!
  • Index(es):
    • Date
    • Thread