- From Linus we have the branch `master` and tags like `v5.10` , `v5.17-rc5`. - From Greg we have branches like `linux-5.10` and tags like `v5.10.93` We want branches on top of the some of these specific commits identified by their tags. These branches should include that tagged upstream version and our mpi specific patches. So I've made the branches `linux-5.17-rc5-mpi` and `linux-5.10.93-mpi` as examples. We use branches (and not tags) here, because we might want to evolve our mpi-patches on top of a specific upstream version. To reference a specific version on our branches, we also need tags here. These are called (for example) `v5.17-rc5-mpi.0` or `v5.10.93-mpi-0`. If we ever change our patches on top of v5.10.93, we could call it `v5.10.93-mpi.1`. These versions can be referenced from a bee file. I've also included the defconfig into this repository (as one mpi-specific commit) with the filename `config-mpi`. So a mpi-tag references a source tree with a included kernel configuration. We can evolve the configuration in `config-mpi` file in this repository and no longer need to include it in the bee file.