git submodules are such broken trash. The only reason we're even using them is to work around the Linux kernel setting EXTRAVERSION with git describe...
So ridiculously bad though. Is there at least a way of automatically dealing with a repo you cloned changing submodule URLs?
Conversation
Replying to
By the way, the Linux kernel doing that is extremely annoying because it means your repository ends up with non-reproducible builds after you add tags.
Our standard approach is building a release, testing it, then tagging the release. We had to change their script for this.
1
3
Not going to rebuild the kernel and then the OS build in order to get it to use a tag. We changed it to always use the kernel.org kernel version with EXTRAVERSION using the git revision rather than trying to opportunistically base the version on the tags.
1
4
Replying to
Be specific about what doesn't work for you. They work perfectly for me. I think a lot of senior developers have tunnel vision / fear around them. All the junior ones I know do great! Kind of weird actually.
RE: URLs, just edit .gitmodules and git commit -am =D
1
Replying to
The part that doesn't work is it will break for everyone else who has a clone of the repository. Also, it's not enough to edit .gitmodules. You need to also fix the remote in the nested repository. There's a git command to handle doing both instead of doing both manually.
1
Show replies