On Wed, 19 Dec 2007 16:58:23 -0800, SJS <[EMAIL PROTECTED]> wrote:
begin quoting MattyJ as of Wed, Dec 19, 2007 at 04:36:05PM -0800:
On Wed, 19 Dec 2007 15:39:28 -0800, SJS <[EMAIL PROTECTED]> wrote:
>begin quoting MattyJ as of Wed, Dec 19, 2007 at 02:57:23PM -0800:
>>On Wed, 19 Dec 2007 14:40:48 -0800, David Brown <[EMAIL PROTECTED]>
>>wrote:
>>
>[snip]
>>I usually try to explain it to my developers by saying that
>>directories do not exist in Perforce. A path/branch exists by the
>>virtue of something being in it (a file.) So directories can't have
>>branches, but files can.
>
>What version-control system *does* version directories?
>
>Any of 'em?
ClearCase is the only one I know of that does it. It's a pretty cool
feature if don't let it get out of hand, but really nice if you need to
re-arrange a directory.
The version I used last year didn't. At least, I never found a way, and
none of the ClearCase advocates on the team bothered to enlighten me.
I was an admin for ClearCase 7 - 8 years ago, just around the time IBM
bought them. I think they were just getting their Lite version underway
and we had sprung for the big, enterprise version (which I think was the
only version they had at the time.) I think it's very different now,
apparently. You used to be able to re-arrange/rename a directory itself,
then you could have all kinds of crazy notations like (not sure I remember
the whole syntax):
/vob/main/project1@@5/assets/html/atria.html@@15
So not only could you have a versioned directory, but different versions
of files in them. If you weren't careful you could really munge the
structure and appear to lose things. But it was nice to be able to
re-arrange a sub-tree, find out that the idea sucked, and roll it back to
how it was before and go at it again.
-Matt
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
