Hello and thanks for the video... Short question: if I have properly seen, it looks like the GIT_SERVER folder has never changed its "look". I mean: although you have committed and pushed changes, the server has never changed. And I can actually understand this, because in order for the changes to be accepted by a server, you should need some "ack" from the server. But what I do not understand is how one can create another project pointing at the same server and still have all committed/pushed changes... although the same do not actually appear in the server folder! Thanks in advance for any explanation you might give... Cheers Nino
I think the GIT Server folder does gets modified/ updated with the changes pushed from either of the Simulink Project folder. One may not be able to observe this because files storage in a GIT repository is in an encapsulated format and cannot be mapped one to one with any file of the content. Moreover, without server folder getting changed it is not possible to get the changes done in one project to reflect in another client. So, I think there is some confusion here in understanding the how GIT Server repository folder works. I hope above explanation helps. Good Luck Programmer World programmerworld.co -
Thanks for the reply, @@ProgrammerWorld. Yes, of course. As I also said, since everything is correctly pulled when you create a new Simulink Project, it is clear that somehow the changes are kept. But here - as you also have said - there is for sure something not fully clear, i.e.: there is some confusion. Simulink is handling GIT in a not straightforward way, when the pointed repository is a folder. I have done the very same as you have done, but by pointing to a remote repository on GitHub. As you may quickly check, in this case, everything is running as expected. Changes performed, committed, and later on pushed are properly appearing 1-to-1 to the remote repository. I think, the way in which Matlab-Simulink handles a local repository might be an interesting topic to unbundle for your fans... ;)
@@antoninomarcosiddiolo5437 Thanks for bringing this up. The reason why you are able to see 1 to 1 mapping in GitHub is because in GitHub what you see is the content of the repository and not the repository folders itself which is hosted on some server. Most likely we can't access those Git servers. Now, in file system, as shown in the video, you are able to see the folders of repository which is not same as folders structure of the content of the repository. Any git repository will always have same folders irrespective of the content being stored. To understand this point, you can create another Git repository and use some other tools like Tortoise Git (apart from Simulink Project) to check out local versions of repository. This will make the whole concept of Git repository much better. Cheers Programmer World programmerworld.co -
Keep it up bro 👍👍
Thanks 😀
Hello and thanks for the video...
Short question: if I have properly seen, it looks like the GIT_SERVER folder has never changed its "look". I mean: although you have committed and pushed changes, the server has never changed. And I can actually understand this, because in order for the changes to be accepted by a server, you should need some "ack" from the server.
But what I do not understand is how one can create another project pointing at the same server and still have all committed/pushed changes... although the same do not actually appear in the server folder!
Thanks in advance for any explanation you might give...
Cheers
Nino
I think the GIT Server folder does gets modified/ updated with the changes pushed from either of the Simulink Project folder. One may not be able to observe this because files storage in a GIT repository is in an encapsulated format and cannot be mapped one to one with any file of the content. Moreover, without server folder getting changed it is not possible to get the changes done in one project to reflect in another client. So, I think there is some confusion here in understanding the how GIT Server repository folder works.
I hope above explanation helps.
Good Luck
Programmer World
programmerworld.co
-
Thanks for the reply, @@ProgrammerWorld. Yes, of course. As I also said, since everything is correctly pulled when you create a new Simulink Project, it is clear that somehow the changes are kept. But here - as you also have said - there is for sure something not fully clear, i.e.: there is some confusion.
Simulink is handling GIT in a not straightforward way, when the pointed repository is a folder.
I have done the very same as you have done, but by pointing to a remote repository on GitHub. As you may quickly check, in this case, everything is running as expected. Changes performed, committed, and later on pushed are properly appearing 1-to-1 to the remote repository.
I think, the way in which Matlab-Simulink handles a local repository might be an interesting topic to unbundle for your fans...
;)
@@antoninomarcosiddiolo5437 Thanks for bringing this up. The reason why you are able to see 1 to 1 mapping in GitHub is because in GitHub what you see is the content of the repository and not the repository folders itself which is hosted on some server. Most likely we can't access those Git servers.
Now, in file system, as shown in the video, you are able to see the folders of repository which is not same as folders structure of the content of the repository. Any git repository will always have same folders irrespective of the content being stored. To understand this point, you can create another Git repository and use some other tools like Tortoise Git (apart from Simulink Project) to check out local versions of repository. This will make the whole concept of Git repository much better.
Cheers
Programmer World
programmerworld.co
-