Just confirming this because git sometimes adds features without me knowing it:
Say you have git repo A,
which has a submodule B,
which has a submodule C.
I want to alter C and use a patched version.
The *only* way to do this is to fork *both* C and B and create unique commits for both of them, right? There's no way for A to say "regardless of what B thinks it wants, override the hash of C"?
@mcc are you in some kind of technology masochism cult?
@gutmunchies @evan This is a more or less unavoidable outcome if anyone is using submodules ever :(
@gutmunchies @evan It is true but they are also practically the only clean way to manage C library dependencies
@mcc @gutmunchies we need a package repository for C
@evan @gutmunchies Proposal: Cargo has many Rust packages which are just wrappers on C libraries, and it can always build the C libraries ok. We should start using cargo to build C programs , and then cargo will manage the C dependencies for us