Re: Version Control [was: Damaging the source code]
Re: Version Control [was: Damaging the source code]
- Subject: Re: Version Control [was: Damaging the source code]
- From: Jean-Daniel Dupas <email@hidden>
- Date: Wed, 4 Nov 2009 10:44:21 +0100
My two cents. AFAIK, if the mini debugger is opened, Xcode do not jump
front when a break point is reached.
Le 4 nov. 2009 à 10:31, email@hidden a écrit :
hi all and thanks for all the responses
about version control:
it is very important to be 'in control' of your versions and for
this one can use special software, but this is not mandatory
to be honest, we have an excellent version control system in that
way that we support mulitple versions of our product and we can
easily migrate from one version to another...this is for us at the
moment
no problem
the fact however that whenever Xcode meets a breakpoint it immediately
directs the keyboard focus to the source code, is troubling me
from the discussion it seems to me that 1) there is not a concensus on
a particular solution and 2) there is no option in Xcode to switch
this
breakpoint-handling to another way
so i will just continue and continue to be very carefull
thanks again and have a nice day :-)
---
perry
On Nov 3, 2009, at 9:16 AM, Jonathan del Strother wrote:
2009/11/2 Jens Alfke <email@hidden>:
Git:
+ Lots of momentum
+ Fast
+ Very powerful command set, esp. for manipulating branches and
merging
+ Distributed
+ Trivial to convert any source tree into a repository
+ Good Subversion interface (lets you mirror an SVN repo and work
with it
using Git)
+ Excellent public repository hosting via GitHub
- Commands have unusual names
- Basic source-file workflow (add / modify / commit) is confusingly
different from anything else, until you get used to it
- Limited GUI support (not sure if there are any Mac apps?)
- Complex installation, adds dozens of commands to your path
- Repositories are not very space-efficient
- Poor Windows support (if that matters to you, i.e. for cross-
platform
code)
I'm curious when you last used git. It now adds only two commands to
your path (git & gitk), everything else is hidden away in libexec.
Repositories are almost always smaller than anything else out there,
although that's sometimes not immediately apparent if, say, you
converted a svn repo to git, but didn't garbage-collect afterwards.
For native Mac GUIs, there's GitX.app, which is fairly good. It
doesn't give a compact enough view of your history for my tastes -
gitk seems to fit way more on screen. git's built-in tcl-tk clients
are functional, if rather ugly.
_______________________________________________
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
_______________________________________________
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
-- Jean-Daniel
_______________________________________________
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