Re: FileMerge trouble with XCode 3.1.x
Re: FileMerge trouble with XCode 3.1.x
- Subject: Re: FileMerge trouble with XCode 3.1.x
- From: Jens Alfke <email@hidden>
- Date: Fri, 23 Apr 2010 08:50:42 -0700
On Apr 23, 2010, at 8:35 AM, Chris Backas wrote:
> I'm migrating my company from XCode 2.5 to XCode 3.1.x on Leopard
> machines. We write software for internal use only, so we take a long
> while to validate our products on new OS releases (in this case
> Leopard)
Your company is still running on a five-year-old unsupported OS?! I thought only Windows shops did that. ;)
Just curious: If you’re catching up now, why are you moving to 10.5 and not 10.6? I would really, really recommend going to 10.6 as there are many improvements in performance, stability and developer tools. Also consider that, if you ever buy any new Macs, they probably won’t run any OS earlier than 10.6. And Apple will probably at some point stop providing security updates to 10.5 just as they did to 10.4.
> Basically, FileMerge (or XCode itself if the option is set that way)
> ALWAYS displays ALL changes as going left to right.
I’m not clear what you mean by this. Do you mean that the older revision is on the left side, and the newer one on the right? That’s determined by the order in which the two files are given to FileMerge. FileMerge itself doesn’t have a notion of ‘older’ and ‘newer’, just ‘left’ and ‘right’.
If you mean the arrows themselves, they’re a bit misleading: they’re only used for merging (when you save a result file), and the arrow head points to which version of a change is going to be incorporated into the merge result. They don’t indicate a direction.
—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