does anyone know of a version control system that allows cloning subtrees as independent repos?
a similar sort of operation possible with some manual effort on git. you can do git surgery to extract a directory's history to its own repo. e.g., when open sourcing a package that's in a big closed-source repo.
but this only works one way. wouldn't be interesting to have something that works both ways? changes to the "sub repo" can make their way to the "parent repo" and they can be kept in sync.
=> More informations about this toot | More toots from sa@chaos.social
@sa sparse checkouts are not what you’re looking for, are they? They’re supported in git and jj.
=> More informations about this toot | More toots from filippo@abyssdomain.expert
@filippo almost! (and thanks i've not seen these before!)
what i'm curious about is how to design a vcs so that these checkouts behave as if they are their own little repos, with no data from other directories in the parent repo leaking in.
sparse checkouts seem to still share the global commit history. you can probably filter these out of the 'git log' output with enough git config, but that's not what i'm interested in!
=> More informations about this toot | More toots from sa@chaos.social This content has been proxied by September (3851b).Proxy Information
text/gemini