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
This Tweet is from a suspended account. Learn more
That's why I bring up repo. That's built for AOSP which is a source tree for far more than the OS. It also has the SDK, massive test suites and many other things. A lot of projects are externally developed with their own Git histories and it's meant to handle forks well, etc.
1
It's meant to let you easily disable / add / change repositories downstream. As a developer, you can replace some of the projects with your own version with a local manifest, etc. It's a lot like submodules but you have a dedicated repository for the metadata and can extend it.
That does sound interesting for more complex pieces of software (and applicable to that case I mentioned in another tweet).
I [luckily] haven't had a need for that yet.