Comments (3)
Hi @inglor,
I'm afraid you have. Unfortunately, due to the way lshistory
works (or at least the way I'm calling it), the history of files that aren't visible from your current view (eg. that are only exist on another branch) don't get returned, and so the history would be misleading/wrong.
This is how I remember the problem, although I vaguely wish I had an instance of Clearcase to confirm. (Although on the other hand I'm also happy if I never have to touch it again).
In any case, it's just a convenience feature when you want to maintain the mapping between a branch and view in a single repo, but it's not anything more than that. I'm sorry it doesn't the much more useful feature of fetching history across multiple branches, which would be extremely handy. The way I was using it, way back when, was to pull in the history of the master/main branch, and then create a new view/branch from that point, and having two branches in git and two views. Obviously at that point that branches in Git diverge - there's no merging/syncing between them.
It sucks. :(
If you can figure out a way to get lshistory
to return history for files not in a view, adding the functionality wouldn't be that hard. I can't remember if I tried the -all
flag, which might do the trick. But again I can't test it.
from git-cc.
If you know if/when the dev branch is merged with master than you can manually create the ci_dev
and cc_dev
branches in Git and start using it. But as mentioned, there's no relationship at that point between master and dev, and you have to rebase both manually from that point onwards.
Not sure if that helps.
from git-cc.
This is what I've been doing for the past weeks.
I created two local dynamic views, one on our production stream and another on our development streeam.
I configured in .git/gitcc:
[develop]
clearcase = m:\my_project_view_sprint_86_int\vob_ccproject
branches = main*|ccproject_sprint_86*
[master]
clearcase = m:\my_project_view_version_00.85.XX_int\vob_ccproject
branches = ccproject_00.85.XX*
(pay attention to the branches part, you can check the lshistory file to see what you should put into each one)
and at the git commits I wanted to start following clearcase, I created the additional branches
master_cc
, develop_cc
and tags master_ci
, develop_ci
I can now use gitcc
in both my develop and master local branches, and they will be linked with the two different views.
A pity about not recognizing deliveries between clearcase streams, but I can live with it.
NOTE: sometimes I run gitcc update
in order to make sure I have all the code in git, because I have seen that from time to time I miss some changes...
NOTE 2: bear in mind that adding manually the _cc
and _ci
branch and tag will tell gitcc not to look at older history from that point back, so depending on where you put them, your first gitcc rebase
might not get all your files
from git-cc.
Related Issues (20)
- would git-cc work properly when cleartool diff is reconfigured? HOT 1
- Unable to initialize gitcc HOT 3
- Changing a symlink into a file in git causes ClearCase checkin to fail HOT 1
- Can I use the program on Linux redhat? HOT 2
- Does the program "git-cc" support python 3.5 HOT 1
- gitcc label erroring out HOT 25
- git-cc fails in subprocess.py HOT 7
- Unable to understand workflow. Where to use git init and where to use gitcc init? HOT 2
- zest.releaser upgrade? HOT 2
- Applying clearcase labels to git commits? HOT 15
- Capturing deleted file history? HOT 6
- git cc rebase - nothing happens HOT 5
- Error during gitcc rebase HOT 1
- Does git-cc support Git to CC HOT 2
- clearcase
- DEBUG in common.py dealt as str after loaded from config file HOT 1
- Only master Branch is creating while migrating but unable to create other branches HOT 1
- Only CC main branch code is migrated for all the branches. HOT 3
- Documentation questions HOT 6
- Version History not reflecting on Git platform HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from git-cc.