Re: Perforce and XCode 2.x not showing revision history ?
Re: Perforce and XCode 2.x not showing revision history ?
- Subject: Re: Perforce and XCode 2.x not showing revision history ?
- From: Steve Mills <email@hidden>
- Date: Thu, 8 Sep 2005 14:46:35 -0500
On Aug 3, 2005, at 16:52, Tom Naughton <email@hidden> wrote:
There's an issue with Xcode's Perforce integration where the results
of the filelog command aren't parsed correctly if your depot is name
something other than '//depot'. This has already been fixed for the
next release.
Do you mean the depot on the server or the name of the local client's
"Root"? Our server depot is named depot, but everyone's local root
name vary from person to person. Having just started using Xcode 2.1
to once again move from CW to Xcode, I've found that Perforce
integration is mostly horrible. Sure, it asks to check files out when
I edit them, but it never enables the Commit menu items, and the Add
to Repository are always enabled even for files that are already in
the depot. I'd love to see the SCM menu reflect terms used by the
current SCM, for instance, "submit" instead of "commit", etc. Those
of us that grew up using nothing but Perforce have to stare at
Xcode's SCM menu for a while until we figure out which menu item it
is that we're after. I'm also spoiled by the Command… item in CW's
Perforce plugin that allows you to type any p4 command without having
to fire up Terminal.
Steve Mills
Drummer, Mac geek
http://sjmills5.home.mchsi.com/
_______________________________________________
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