gitcc label erroring out

I am using cc2git label
gitcc checkin --cclabel=YOUR_EXISTING_CC_LABEL

getting error
Usage: gitcc [options]
gitcc: error: --cclabel option does not take a value

Yeah, I don't think this was ever actually tested:

42db799

Would need a change to optparse to specify the type as string:

git-cc/git_cc/gitcc.py

Line 36 in 01a35a3

option = {

Can you make the change and I can retest?

@amousa1968 I'm not going to lie. I haven't used Clearcase (and Python) in almost 10 years. If I thought it would be the last ever change you need to get things working I would be happy to make the change if I got a spare second. But git-cc is definitely not battle-hardened, and this kind of bug is what you can really expect with the whole git-cc experience.

For now I suggest you not use --cclabel and see how far you get. If everything else works fine and want --cclabel then I'll have a quick stab at fixing the bug for you.

Another way of putting it - git-cc is unfortunately/mostly an orphaned project and you really have to be willing to fix or workaround whatever bugs you find. Sorry. :(

Thanks, I'll try it.

Let me if you could add it to the file since your more familiar with the code. Thanks Ayman Mousa

…

On Dec 11, 2016, at 9:26 PM, charleso ***@***.***> wrote: Yeah, I don't think this was ever actually tested: 42db799 Would need a change to optparse to specify the type as string: https://github.com/charleso/git-cc/blob/01a35a3a5f4e387c2b95feeafd6778a83ea679bd/git_cc/gitcc.py#L36 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

Let me if you could add it to the file since your more familiar with the code.

What happens if you don't specify --cclabel, does git-cc work for you?

Not yet. I’ll let you know today. One other question I had for you before this one. Take a look at the 2nd ticket? #73 1. Does it support py3.5.2 2. Where do I change git remote URL From: charleso [mailto:notifications@github.com] Sent: Sunday, December 11, 2016 8:16 PM To: charleso/git-cc <git-cc@noreply.github.com> Cc: amousa1968 <amousa@cox.net>; Mention <mention@noreply.github.com> Subject: Re: [charleso/git-cc] gitcc label erroring out (#75) Let me if you could add it to the file since your more familiar with the code. What happens if you don't specify --cclabel, does git-cc work for you? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#75 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AVLIbDuOkbKyqJHMmrgDSUooNUHFaqbgks5rHMpwgaJpZM4LKIAY> . <https://github.com/notifications/beacon/AVLIbFLrnK3unmTbRg2W4SPOdijTRzh8ks5rHMpwgaJpZM4LKIAY.gif>

@amousa1968 I don't want to be rude, but I guess this is the kind of extra leg work you're going to need to do to get git-cc working. There is no documentation, it's very bad/old code.

I don't know whether python 3.5 is supported, from that error I suspect it is but you have something strange in your configuration or windows path name.
What Git remote URL

Hi Forgot to email you and let you know the git-cc worked but had to make some changes to the program. I will update github with the changes after it all issues has been resolved. Thanks From: charleso [mailto:notifications@github.com] Sent: Sunday, December 11, 2016 8:16 PM To: charleso/git-cc <git-cc@noreply.github.com> Cc: amousa1968 <amousa@cox.net>; Mention <mention@noreply.github.com> Subject: Re: [charleso/git-cc] gitcc label erroring out (#75) Let me if you could add it to the file since your more familiar with the code. What happens if you don't specify --cclabel, does git-cc work for you? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#75 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AVLIbDuOkbKyqJHMmrgDSUooNUHFaqbgks5rHMpwgaJpZM4LKIAY> . <https://github.com/notifications/beacon/AVLIbFLrnK3unmTbRg2W4SPOdijTRzh8ks5rHMpwgaJpZM4LKIAY.gif>

Hey Buddy, Happy holidays and new year!!!! Here is the latest update. 1. I had to make some changes to the scripts gitcc label update/gitcc update/ and .gt/gitcc to make the process work. 2. Created shell script that executes each step in the process. I have question for you and I am having hard time to understand how does the program works and calls each step in .git/gitcc Can you explain this to me where does the .git folder needs to live under to be able to use it properly. exclude = FolderA/sub/folder|FolderB/other/file I have git-cc directory structure like this C:\ git_migration\GitHub\git-cc Under git-cc There is Inside test_script contains the migrated clearcase label/tag directory structure We created .gitignore file under git-cc folder We like to exclude directories from inside test_script directories and here is the format we used Exclude = test_script/a folder/build/matlab/| test_script/a folder/scu/FTCA/ test_script/a folder/tools/matlab/ We tried it but those folders appears to be in git. Can you advise what is the proper of doing it? Thanks Ayman From: charleso [mailto:notifications@github.com] Sent: Sunday, December 11, 2016 8:16 PM To: charleso/git-cc <git-cc@noreply.github.com> Cc: amousa1968 <amousa@cox.net>; Mention <mention@noreply.github.com> Subject: Re: [charleso/git-cc] gitcc label erroring out (#75) Let me if you could add it to the file since your more familiar with the code. What happens if you don't specify --cclabel, does git-cc work for you? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#75 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AVLIbDuOkbKyqJHMmrgDSUooNUHFaqbgks5rHMpwgaJpZM4LKIAY> . <https://github.com/notifications/beacon/AVLIbFLrnK3unmTbRg2W4SPOdijTRzh8ks5rHMpwgaJpZM4LKIAY.gif>

Hi @amousa1968.

Can you explain this to me where does the .git folder needs to live under to be able to use it properly.

What commands have you run so far? Do you have a separate git repository created by/for git-cc? It will have a .git folder inside it, which is the one you need to look at.

Hi. .git folder is under git-cc folder. Did you see the screenshot emailed you earlier? Thanks Ayman Mousa

…

On Dec 21, 2016, at 1:32 PM, charleso ***@***.***> wrote: Hi @amousa1968. Can you explain this to me where does the .git folder needs to live under to be able to use it properly. What commands have you run so far? Do you have a separate git repository created by/for git-cc? It will have a .git folder inside it, which is the one you need to look at. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

Did you see the screenshot emailed you earlier?

Github doesn't show images sent from email replies.

.git folder is under git-cc folder.

Um, that's the wrong .git folder. You need to run git init and the other commands in the README in a new folder that's different from git-cc. For example:

C:\git_migration\GitHub\mygitrepository

I'll resend it. Thanks Ayman Mousa

…

On Dec 21, 2016, at 2:33 PM, charleso ***@***.***> wrote: Did you see the screenshot emailed you earlier? Github doesn't show images sent from email replies. .git folder is under git-cc folder. Um, that's the wrong .git folder. You need to run git init and the other commands in the README in a new folder that's different from git-cc. For example: C:\git_migration\GitHub\mygitrepository — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

Answer your questions:- 1. .git folder is in a separate folder. To be clear here is the setup looks like. C:\migration_project Under this folder there is another folder for git-cc. C:\migration_project\git-cc This folder contains all of the git-cc scripts 2. I have another folder named "raptor" and .git lives under this folder, and this folder was created by gitcc update after cleartool, and gitcc init and git init 3. We went through the steps after gitcc update and we skipped gitcc rebase because we're running base clearcase. 4. Under .git we have updated the config file the include and exclude but the exclude seems not to be working. Can explain how does the exclude works? Thanks Ayman Mousa

…

On Dec 21, 2016, at 1:32 PM, charleso ***@***.***> wrote: What commands have you run so far? Do you have a separate git repository created by/for git-cc? It will have a .git folder inside it, which is the one you need to look at.

We went through the steps after gitcc update and we skipped gitcc rebase because we're running base clearcase.

update was really added originally as a bootstrap, but it wasn't implemented very well. update calls sync.py, which can you see in this file doesn't look at the Exclude value:

https://github.com/charleso/git-cc/blob/master/git_cc/sync.py#L51

You can see it working here correctly for rebase:

https://github.com/charleso/git-cc/blob/master/git_cc/rebase.py#L215

Not sure what you mean "because we're running base clearcase", what has that got to do with rebase? It was originally written for base clearcase, and should work fine.

If your using UCM clearcase then the rebase is recommended but if your using base clearcase you don't need the rebase. Hope this does help. Thanks Ayman Mousa

…

On Dec 21, 2016, at 6:13 PM, charleso ***@***.***> wrote: We went through the steps after gitcc update and we skipped gitcc rebase because we're running base clearcase. update was really added originally as a bootstrap, but it wasn't implemented very well. update calls sync.py, which can you see in this file doesn't look at the Exclude value: https://github.com/charleso/git-cc/blob/master/git_cc/sync.py#L51 You can see it working here correctly for rebase: https://github.com/charleso/git-cc/blob/master/git_cc/rebase.py#L215 Not sure what you mean "because we're running base clearcase", what has that got to do with rebase? It was originally written for base clearcase, and should work fine. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

If your using UCM clearcase then the rebase is recommended but if your using base clearcase you don't need the rebase. Hope this does help.

Apologies, git-cc rebase is a git-cc command which is poorly named and has nothing to do with UCM rebase. It works equally for both base and UCM. It should have been called pull or something else.

Great thank you for the clarification . Thanks Ayman Mousa

…

On Dec 21, 2016, at 8:47 PM, charleso ***@***.***> wrote: If your using UCM clearcase then the rebase is recommended but if your using base clearcase you don't need the rebase. Hope this does help. Apologies, git-cc rebase is a git-cc command which is poorly named and has nothing to do with UCM rebase. It works equally for both base and UCM. It should have been called pull or something else. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

Hi everyone, Sorry for the delay, merry Christmas, and happy holidays! Here is the steps taken: 1. Downloaded git-cc from C:\> pip install git+git://github.com/charleso/git-cc.git#egg=git_cc 2. Install python 3.5.2 3. Install setuptools 4. C:\test_project> pip install . 5. C:\test_project> git init 6. C:\test_project> Create .git/gitcc file 7. Add the following a. [core] b. include = FolderA|FolderB c. exclude = FolderA/sub/folder|FolderB/other/file d. debug = True 8. clearcase = C:\snapshot_views\vob_migrate\raptor 9. gitcc init C:\snapshot_views\vob_migrate\raptor 10. gitcc update 11. git add . 12. git commit -m "initial comments" 13. git tag <label & date> 14. gitcc tag <label & date> a. execute output steps 15. gitcc checkin 16. git lfs install 17. git push origin master 18. gitcc push origin output steps 19. verify steps in git Note, we tried to exclude few directories from C:\snapshot_views\vob_migrate\raptor for git so they don’t get pushed to git, and we have them listed on the ignoregit file. It did not seems to work. Let me know if a step is missing in the process? From: charleso [mailto:notifications@github.com] Sent: Wednesday, December 21, 2016 8:48 PM To: charleso/git-cc <git-cc@noreply.github.com> Cc: Downforce Autosport <amousa@cox.net>; Mention <mention@noreply.github.com> Subject: Re: [charleso/git-cc] gitcc label erroring out (#75) If your using UCM clearcase then the rebase is recommended but if your using base clearcase you don't need the rebase. Hope this does help. Apologies, git-cc rebase is a git-cc command which is poorly named and has nothing to do with UCM rebase. It works equally for both base and UCM. It should have been called pull or something else. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#75 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AVLIbN12fOeiQiKKlTmPFinmbMZ--Om7ks5rKgDngaJpZM4LKIAY> . <https://github.com/notifications/beacon/AVLIbEAjAwKsYbtuzG2zUkhVfN21NMoVks5rKgDngaJpZM4LKIAY.gif>

Hi @amousa1968, and Merry Christmas to you too.

As mentioned previously update doesn't respect the Exclude configuration. You can either fix the python code, or alternatively add a .gitignore file to the git repository which should prevent those files being added (much easier).

I'm curious, where does gitcc push come from?

The gitcc push right after git push to master, that was not included in the readme file. If you only do git push to master it will push without the tag, therefore we found out gitcc push was needed at the end of the steps and after all the tag will show up. Once I finalize the steps I’ll update the repo. From: charleso [mailto:notifications@github.com] Sent: Tuesday, December 27, 2016 2:37 PM To: charleso/git-cc <git-cc@noreply.github.com> Cc: Downforce Autosport <amousa@cox.net>; Mention <mention@noreply.github.com> Subject: Re: [charleso/git-cc] gitcc label erroring out (#75) Hi @amousa1968 <https://github.com/amousa1968> , and Merry Christmas to you too. As mentioned previously update doesn't respect the Exclude configuration. You can either fix the python code, or alternatively add a .gitignore file to the git repository which should prevent those files being added (much easier). I'm curious, where does gitcc push come from? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#75 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AVLIbLqIKhCGW3WiS4lSyGJRVGlsAzXwks5rMZLvgaJpZM4LKIAY> . <https://github.com/notifications/beacon/AVLIbIR_BlMW8WohB_avKkv-DAGsCG9nks5rMZLvgaJpZM4LKIAY.gif>

Hi buddy,

I nailed down the gitcc process and the program has been running for 2 days to push 114 labels from clearcase to git, and i tailed the log file to see what is going on and why it is taking time. This is what I found out during the process gitcc update step it is copying files from CC snapshot vob to the gitcc working folder and the copy is taking long long time and it's taking 2 to 3 hours each time while its copying over 7000 to 11000 files. I don't want to modify gitcc update script unless I check with you how do I speed up the process while its executing gitcc update command

@amousa1968 As mentioned before the way git-cc was designed to work is to run the rebase command. That uses lshistory to work out what was changed since the last rebase and only add the changes. It's not without problems, but update was really only added to get people started if their initial history was too big/complicated.