begin quoting Michael O'Keefe as of Tue, Jul 05, 2005 at 12:11:47PM -0700: [snip] > >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? [snip] > >....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. Yes. For Very Large Projects, you don't take up local diskspace. [snip] > >>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] Neat. So do you see @@ directories with "ls" ? % ls Makefile Makefile@@ foo.c foo.c@@ foo.h foo.h@@ % [snip] > >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. Ah... > 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 Was CC your first? > Or did you mean a day-in-the-life of a DO ? If so, I replied to another > with an answer to that Nah, I was looking for a day-in-the-life-of-CC. > > "Every version management system should have a thick manual" > > They do, that's prolly the problem :( Nah, if there's a problem, it's probably because the manual wasn't well-written. -Stewart "Documentation is the hardest thing to write in software" Stremler
pgpTGjZ7WYZOQ.pgp
Description: PGP signature
-- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
