Should we consider using repo to manage our set of repositories?
Then we can create cross-repository branches and more easily update a set of local repositories.
If you have proposals for cross-repo management, you should very quickly put together a RFC for issue 13. The rules for RFCs are here.
Since everybody who took part in the conversation is basically in agreement, I believe that @jlorenzo is planning to close the conversation soon and proceed with the one-repo multi-crate plan (which I personally believe is near ideal).
Having a single repo is even better,
I’ve just had lots and lots of grief having multiple repos and not having things in sync.
[dhylands] dhylands
https://discourse.mozilla-community.org/users/dhylands Dave Hylands
https://discourse.mozilla-community.org/users/dhylands
April 16Should we consider using repo to manage our set of repositories?
Then we can create cross-repository branches and more easily update a
set of local repositories.
Only for the sake of discussing (because we basically agreed on the 1
repo / several crates solution), I don’t get what repo brings over cargo
? It seems to me Cargo.toml brings everything repo brings. Except
possibly for non-rust stuff like the openzwave library ?