Reputation: 20698
Continuing from my earlier query:
Trying to migrate to Git from Clearcase, but people keep asking these questions because they've designed their bureaucracy around Clearcase:
1. Is there an equivalent for Clearcase streams in Git? If not, how is it managed in Git?
2. What is the Git equivalent for a Clearcase view?
3. Clearcase has locks that the admin can use to protect files from unauthorized use. I understand Git depends on file/folder permissions, but in an Enterprise environment, would it really be possible to implement a secure environment for Git, with user specific permissions and firewall protection?
Upvotes: 2
Views: 608
Reputation: 1329092
1/ Is there an equivalent for ClearCase streams in Git? If not, how is it managed in Git?
No: a stream is an UCM metadata allowing you to declare components and share a common configuration among different UCM views for different users (all referring to the same stream)
The closest would be to add in a main Git repo gitlinks to submodules.
And you can make a submodule follow a branch if you need to.
2/ What is the Git equivalent for a ClearCase view?
A git clone
: you get what is similar to a snapshot view, except you can change its configuration locally at any time (make new branches, switch or merge branches).
3/ ClearCase has locks that the admin can use to protect files from unauthorized use. I understand Git depends on file/folder permissions, but in an Enterprise environment, would it really be possible to implement a secure environment for Git, with user specific permissions and firewall protection?
Yes, on a blessed server for managing blessed repo.
Not on local cloned repo (where each developer does what he/she wants).
You can control who push/pull what on/from that blessed server, if you add an authorization layer like gitolite (See "How do programs like gitolite work?" and its VREF in an example).
See more at "Distributed Version Control Systems and the Enterprise - a Good mix?".
Upvotes: 2