Know how else git submodule is broken? git grep in a submodule doesn't work. While grep -r XXX . does.
Conversation
This Tweet is from a suspended account. Learn more
Like a recursive grep but it understands what's not part of the source tree and can be used on any commit, etc. rather than simply what you have checked out at the moment. It's quite useful simply for not looking in .git, build output, etc. without excluding that stuff.
1
1
This Tweet is from a suspended account. Learn more
This Tweet is from a suspended account. Learn more
I think subtrees make more sense for tightly bound components and repo is a nicer approach than submodules for other things.
Submodules are bad enough that both AOSP and Chromium invented their own versions of it to work around how broken/weird/painful they are to deal with.
2
1
Yeah, I won't ever use/introduce submodules into a project if I can avoid it. I'm 100% for subtrees. Mainly because today's software w/ things like leftpad/mimemagic causing pain.
2
I don't mind repo because it's simply a text file describing repositories via branch, tag, revision, etc. and it's nice to deal with for overriding repositories and so on. It essentially works like submodules if you reference things via revision which you do for a release.
2
Like submodules, but without totally breaking Git, basically... so it's just a bunch of separate Git repositories and Git's tooling isn't totally screwed up by using it. I find submodules to be ridiculously painful to deal with and it always goes wrong... I don't get it.
I wouldn't mind the submodules if they actually came w/ the git clone, because in almost ALL cases (I can't really think of a case otherwise) you want the submodules to be checked out.
1
And then half the build infra won't actually check to make sure that you've checked out the submodules, and will fail w/ strange error messages and not even tell you that you forgot to check them out.