This project is licensed under the Apache 2 with LLVM exception license. For a more complete discussion of this project's licensing, see [LICENSE-DETAILS.md].
NOTE: the repo (and rustc_apfloat-git-history-extraction) might be public already, but only for convenience of discussion, see relevant Zulip topic for more details.
TODO(eddyb): "port" terminology a bit messy? is there a better word?
Branches are used as "layers":
llvm-${LLVM_COMMIT}-port: C++ -> Rust port from upstream (LLVM)- all fixes for porting mistakes, and non-functional changes go here
- TODO(eddyb): which branch gets e.g. Rust API changes? oldest or newest?
llvm-f3598e8-portfor https://github.com/llvm/llvm-project/commit/f3598e8fca83ccfb11f58ec7957c229e349765e3
- all fixes for porting mistakes, and non-functional changes go here
llvm-${LLVM_COMMIT}-critical-backports: extra patches from upstream (LLVM)- based on
llvm-${LLVM_COMMIT}-port, plus any C++ -> Rust backports that cannot wait for a full "port bump" (for the lack of a better term) llvm-f3598e8-critical-backportson top ofllvm-f3598e8-portfor https://github.com/llvm/llvm-project/commit/f3598e8fca83ccfb11f58ec7957c229e349765e3
- based on
llvm-${LLVM_COMMIT}-upstreaming: extra patches for later upstreaming (to LLVM)- based on
llvm-${LLVM_COMMIT}-critical-backports, plus any fixes we've made to Rust code ported from buggy C++, which should eventually be upstreamed back into LLVM (under the assumption that LLVM wants the same bugfix) llvm-f3598e8-upstreamingon top ofllvm-f3598e8-critical-backportsfor https://github.com/llvm/llvm-project/commit/f3598e8fca83ccfb11f58ec7957c229e349765e3- FIXME(eddyb): should the above links be formatted into a table?
- based on
main: latestllvm-${LLVM_COMMIT}-upstreaming, i.e. "the most stacked changes"- this is where
crates.ioreleases will eventually come from, too
- this is where