You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copyright in the original liballoc code rests with each individual contributor, albeit dual-licensed by them under MIT and Apache-2.0 at user discretion. I'm happy for copse to adopt the same approach for its contributions.
However, correctly attributing copyright therefore requires incorporating liballoc's git history into this repo (albeit that should also ease tracking/merging of upstream changes in future too).
Unfortunately that's not entirely straightforward, as git doesn't enable one to link only to another repo's subfolder: we'll probably need to maintain our own fork of the entire rust-lang/rust repo, include that fork as a submodule, and then (I guess) use a #[path] attribute to set our btree module to use the relevant file from that submodule?
I'm not 100% clear about this however: will investigate, or else any suggestions/PRs welcome!
The text was updated successfully, but these errors were encountered:
After a little research, I'm leaning toward a strategy based upon (periodic/scheduled) automated git subtree split of liballoc's btree folder into a temporary repo, followed by a subtree pull that merges any changes into this repo's copy of that folder.
As part of #2, I'll be looking into whether there are any GitHub actions out there that will do this by opening a PR (which would be ideal).
Copyright in the original liballoc code rests with each individual contributor, albeit dual-licensed by them under MIT and Apache-2.0 at user discretion. I'm happy for copse to adopt the same approach for its contributions.
However, correctly attributing copyright therefore requires incorporating liballoc's git history into this repo (albeit that should also ease tracking/merging of upstream changes in future too).
Unfortunately that's not entirely straightforward, as git doesn't enable one to link only to another repo's subfolder: we'll probably need to maintain our own fork of the entire rust-lang/rust repo, include that fork as a submodule, and then (I guess) use a
#[path]
attribute to set ourbtree
module to use the relevant file from that submodule?I'm not 100% clear about this however: will investigate, or else any suggestions/PRs welcome!
The text was updated successfully, but these errors were encountered: