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"
So is there the concept of a commit? Or if I make a change to foo.c,
you see that change right away? Or is it that I can make all the
changes I want, and when I commit, those files have been updated in your
tree?
Yes, it's not like native NFS where changes are instantly done when you
save your files. But like the original comparison stated, there isn't an
atomic commit.
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)
<snip>
Neat. So do you see @@ directories with "ls" ?
% ls
Makefile Makefile@@ foo.c foo.c@@ foo.h foo.h@@
No. You have to specifically state the @@ to see it.
I never tried 'ls *@@/.' though (that I recall)
And I don't recall if find wasted time walking the @@ directory
<snip>
Was CC your first?
No, CVS was (on large projects of course)
I used CC for prolly 5 or 6 years across 2 companies
I don't recall what I used directly before CC
--
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
