Hi Michele, no problem, I respect you time and did not bother any more.
I do not know why everything was setup to point to scm.trinitydesktop.org. In any case when I updated the root/base repo (tde) it did not update automatically the submodules and every time I did git pull it was spitting the warning. There were two problems: 1st it was slow to pull from scm and second I am not authorized to push to scm (I know what scm is, no need to explain) Perhaps the issue was introduced because I pulled from scm. I do not recall anymore. It was many years ago. I wrote a script that updated all the submodules to use remote @TGW. Now it is faster and no problem with push anymore.
Ok, thanks for the explanation Emanoil. The reason everything is still pointing to scm is mostly historical, since gitea and TGW only came into the picture in 2018. Glad to hear all is good now. Cheers Michele