Report
5 years, 8 months ago.

To commit in this program, you need to commit changes in library... ?

I have imported and modified program for a SolderSplash WiFiDipCortex board. I have made changed to the program and to the included TI cc3000 WiFi Library. I would like to start using version control to save my changes to went to commit the changes I have made. I'm nowhere near being ready to publish changes. I would like to share my software with a colleague. When I press the COMMIT button the messgage I get is

to commit in this program, you need to commit changes in library

I don't want to publically save changes to the original program as I have hacked it to death, and want to save/commit/publish it as a new and different program completely. How do I do these things?

Im not ready to commit changes publically to the CC3000 library as I'm not sure yet if the changes are correct, but will do in time. How do I do this.

I apologise in advance if this information is easily available and I haven't been looking in the right place.

GH

Comment on this question

2 Answers

5 years, 8 months ago.

In adition to Martin's answer, sometimes you don't want to publish the new library, even as non-public, for whatever reason. You can then right mouse button on the library, convert to folder. Then it is just another folder and you can commit your program without committing the library. However do take into account that this breaks the link with the original library: you cannot create pull requests anymore with it (even if you do make it a library again), and also no version history to compare it to older versions anymore.

Eric, Very helpful - thank you. Giles

posted by Giles Hutchison 21 Nov 2013
5 years, 8 months ago.

Hello Giles Hutchison,

are you using cc3000 host driver? I would like to see changes you made.

Back to your question, commit changes in the library, you will fork the library. It will ask you once you are about to publish, to fork it or to push those changes to the original library. A notification will pop up.

After you commit + fork the cc3000 library, commit and then publish your example which you can share with your colleague. You can publish it as public (anybody can see it), public unlisted (only those who have a link), private.

Regards,
0xc0170

Martin, Thanks for the feedback. I'm not ready to commit changes publicly to the CC3000 library as I'm not sure yet if the changes are correct, but will do once tested. Giles

posted by Giles Hutchison 21 Nov 2013

Giles, it might be worth having a read of http://mbed.org/handbook/Collaboration/Getting-started . Specifically - committing is not the same thing as publishing. Committing just creates an internal checkpoint in your program.

posted by Dan Ros 21 Nov 2013