|
⇤ ← Revision 1 as of 2008-06-05 22:36:46
Size: 763
Comment:
|
Size: 847
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 14: | Line 14: |
| From there you can push the repository anywhere you like. As you pick up updates via rebasing in Clearcase and updating your snapshot view, {{{hg status}}} will tell you what is out of sync with your repository. {{{hg addremove}}} is a wonderful command to keep files in sync with respect to new files and deleted files. | From there you can push the repository anywhere you like. === Clearcase to Hg === As you pick up updates via rebasing in Clearcase and updating your snapshot view, {{{hg status}}} will tell you what is out of sync with your repository. {{{hg addremove}}} is a wonderful command to keep files in sync with respect to new files and deleted files. === Hg to Clearcase === This is a little tougher. |
Information for Clearcase/UCM Users
Clearcase/UCM Concepts
Syncing with a Mercurial Repository
It's simple enough to have a stream in Clearcase coexist with a Mercurial repository. All you need is to create a snapshot view on the stream in question. After the files are updated and on a local disk, turn the snapshot view into a Mercurial repository.
hg init hg addremove hg ci -m "Initial checkin"
From there you can push the repository anywhere you like.
Clearcase to Hg
As you pick up updates via rebasing in Clearcase and updating your snapshot view, hg status will tell you what is out of sync with your repository. hg addremove is a wonderful command to keep files in sync with respect to new files and deleted files.
Hg to Clearcase
This is a little tougher.