New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

All the version on all branches of CC will be created to master branch of git, is it reasonable? #41

Open
hanjie0 opened this Issue Mar 7, 2014 · 1 comment

Comments

Projects
None yet
2 participants
@hanjie0

hanjie0 commented Mar 7, 2014

When we transfer between CC main and git master.

We run "cleartool lshistroy" and then filter "checkinversion operaton" to get all the versions created. )
Typically, the output might be

checkinversion|20140307.1111111|user|dummy|\main\5| (it is a version on Main)
checkinversion|20140307.1111111||dummy|\main\my_branh\5| (it is a version on my_branch)

And then we
cc_exec(['get','-to', toFile, cc_file(file, version)])

And then create git version on master for each of them.
This will create some addtional version on the git master, which are original on the my_branch of CC
is it reasonable?

@charleso

This comment has been minimized.

Show comment
Hide comment
@charleso

charleso Mar 7, 2014

Owner

HI hanjie0,

I'm not sure what the question is? That all sounds like what git-cc does, although you lose me at the end when you're talking about "additional version on the git master".

As you've probably noticed git-cc doesn't do anything clever about Clearcase (or Git) branches. It's assuming that you will want to sync a single view/branch. Anything else in Clearcase is just too hard because of the way it tracks branching on a per-file basis. So whatever branch you're on in Git is the branch that will updated from Clearcase changes which are controlled by the branches configuration (or main by default).

Does that help or make sense? I wish git-cc could have been smarter. :(
Charles

Owner

charleso commented Mar 7, 2014

HI hanjie0,

I'm not sure what the question is? That all sounds like what git-cc does, although you lose me at the end when you're talking about "additional version on the git master".

As you've probably noticed git-cc doesn't do anything clever about Clearcase (or Git) branches. It's assuming that you will want to sync a single view/branch. Anything else in Clearcase is just too hard because of the way it tracks branching on a per-file basis. So whatever branch you're on in Git is the branch that will updated from Clearcase changes which are controlled by the branches configuration (or main by default).

Does that help or make sense? I wish git-cc could have been smarter. :(
Charles

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment