Re: Why does SCM have to be so ....... hard?
Re: Why does SCM have to be so ....... hard?
- Subject: Re: Why does SCM have to be so ....... hard?
- From: Daryle Walker <email@hidden>
- Date: Sun, 19 Sep 2004 16:11:37 -0400
On Sep 18, 2004, at 12:52 PM, Christoffer Lerno wrote:
Could anyone give me pointers on how to use SCM on xcode without it
being slow torture?
I really want to get started with it, but somehow I instead spend
countless hours just trying to get a single commit to work, and for it
to be of any use for me it has to work transparently.
Quite possibly I'm doing something seriously wrong. I just want things
to work like this:
1. Creating a new file automatically adds it to my repository
2. Editing a file automatically checks it out.
I guess you really mean "marks it for editing". (A file has to be
checked out first to be available for any kind of local work!) This is
really applicable only for SCM systems that use exclusive locks. Other
systems (like CVS) assume that files are always editable, and worry
about conflicts (from multiple editors) only upon check-in.
3. Saving a file commits it to the repository
This would be really annoying for people (like me) who save a file many
times before finishing a complete change, especially if commit comments
are required.
4. Removing a file from the project commits this change to repository
Undoing this would probably still need to be done manually.
I can't seem to get that working. Instead I have to commit all and
every change manually, which means the usefulness drops to almost
nothing for me since it's a one person project.
On the other hand IntelliJ IDEA has SCM like this built in without
having to fiddle anywhere.
Unless there's an option to turn off these "features," remind me to
never get this product.
Am I overlooking something?
Yes. Having an instant commit on every file creation, save, and delete
would block having a single commit based on a bunch of changes
en-masse. (Imagine splitting a single header/source file pair into
several.) It is critical to have atomic mass commits so you can't
accidentally retrieve an intermediate state that breaks the build.
--
Daryle Walker
Mac, Internet, and Video Game Junkie
darylew AT mac DOT 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