Conversation

This Tweet is from a suspended account. Learn more
Replying to and
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
Replying to and
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
Replying to and
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
Replying to and
I wouldn't call it a build tool. It's a fairly straightforward script for managing a bunch of Git repositories. It's comparable to making a top-level repository with everything else as submodules, but without the pain of submodules, and very unopinionated about how you use it.
1
1
This Tweet is from a suspended account. Learn more
Show replies