• 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: Refactoring class names, Xcode and git.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Refactoring class names, Xcode and git.


  • Subject: Re: Refactoring class names, Xcode and git.
  • From: Jens Alfke <email@hidden>
  • Date: Wed, 13 May 2015 10:18:02 -0700


On May 13, 2015, at 9:52 AM, Alex Zavatone <email@hidden> wrote:

It appears that I may have uncovered an issue with how Xcode deals with files refactored this way in Git.

It definitely sounds like an Xcode bug. I don’t think Git itself has trouble with case changes, although I know case-folding filesystems like HFS+ are tricky for version-control systems.

Honestly, I avoid committing from Xcode if anything nontrivial is going on. Too often Xcode’s done the wrong thing, like committing files from submodules when I told it not to. I highly recommend the free SourceTree app, which is a very nice GUI front-end to Git (and Mercurial.) That’s where I do most of my heavy lifting.

—Jens
 _______________________________________________
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: 
 >Refactoring class names, Xcode and git. (From: Alex Zavatone <email@hidden>)

  • Prev by Date: Re: Refactoring class names, Xcode and git.
  • Next by Date: Re: Refactoring class names, Xcode and git.
  • Previous by thread: Re: Refactoring class names, Xcode and git.
  • Next by thread: Warning: usage of --preserve-metadata with option "resource-rules" (deprecated in Mac OS X >= 10.10)!
  • Index(es):
    • Date
    • Thread