You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just reread the git submodule man pages, whatever links I could find and came to the conclusion that:
Git submodules are tragically flawed and downright evil
There is no possible way to set things so that branches are automatically tracked and easily refreshed to the latest commits
At the moment, several of the submodule commits are behind the latest master HEADS. If I were to refresh them, they would be again be behind upon the next commit in any of the projects.
I think the easiest solution is to abandon the notion of pipes-platform, and wind down the notion of pipes-platform, perhaps starting again with pipes-examples ie a clean repo to place extended examples etc.
The text was updated successfully, but these errors were encountered:
I just reread the
git submodule
man pages, whatever links I could find and came to the conclusion that:At the moment, several of the submodule commits are behind the latest master HEADS. If I were to refresh them, they would be again be behind upon the next commit in any of the projects.
I think the easiest solution is to abandon the notion of pipes-platform, and wind down the notion of pipes-platform, perhaps starting again with
pipes-examples
ie a clean repo to place extended examples etc.The text was updated successfully, but these errors were encountered: