I don't like "copy-to-local" CRM systems.
With CC being NFS, you don't need to wait around while you come up to
date. You are always live (under the control of your client-spec, of course)
The upside of always being live is what? Every save can be undone? Or
does it force continuous integration?
When I come in and sync (copy) up all the checkins of everyone, it can
take a HUGE amount of time. With CC, it's always available right now.
That's what I meant by "live"
I loved that I can have multiple xterms up, and see the same code with
different viewspecs at the same time without doing anything other that
requesting different labels in this view.
....and taking up local disk space with the multiple versions.
For Very Large Projects, that's probably a good thing. :)
I'm not sure I follow. There was no "local" disk space in CC.
The client-spec is a "filter" on what you see. It's *all* available if
you want to see it, but your spe (typically) says "I just want to see
the latest-and-greatest of such and such". But when you want to work on
a frozen code-line, you say "only show me code labelled with V2.6.2rc4"
Now, when someone would come to me and say "I've got a problem with this
code" I could popup an xterm, go see that code without having to a
single thing
That I can view any version of a file (in any branch) instantly by using
the backdoor '@@' directory is fabulous
How does that work? You cd into @@ and you see an exploded history?
Yes. If you have a file called 'Makefile' for example, you could cd in
'Makefile@@' and see every version of the file (numbered numerically),
and every branch was a subdirectory. There are also symlinks/hardlinks
for labels. There is always a /main/LATEST for every file, that is the
latest-and-greatest. So using the backdoor, you could look at
Makefile@@/main/LATEST, even if your client-spec says you want to see
[EMAIL PROTECTED]
And I *REALLY* loved the time it cut down on building large systems
becoz of it's DO subsystem. Now that I'm using PerForce (a copy-to-local
CRM), if someone changes a major header, EVERYBODY has to rebuild :(
DO?
"Derived Object", perchance?
How about a day-in-the-life sort of example?
Unfortunately, the Principal Engineer I've been under for about 3 years
now came from a Perforce background, and I've been forced to live under
it. I can't recall details of a day-in-the-life of CC now. All I can
tell you is that everytime P4 get's in my way, I wish I was still using CC
Or did you mean a day-in-the-life of a DO ? If so, I replied to another
with an answer to that
-Stewart "Every version management system should have a thick manual" Stremler
They do, that's prolly the problem :(
--
Michael O'Keefe | [EMAIL PROTECTED]
Live on and Ride a 03 BMW F650GSDakar| [EMAIL PROTECTED] / |
I like less more or less less than |Work:+1 858 845 3514 / |
more. UNIX-live it,love it,fork() it |Fax :+1 858 845 2652 /_p_|
My views are MINE ALONE, blah, blah, |Home:+1 760 788 1296 \`O'|
blah, yackety yack - don't come back |Fax :+1 858 _/_\|_,
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
