Jonathan Wakely <jwakely....@gmail.com> writes: > Is there a reason you can't just make it a branch of the GCC repo? > > It would mean you need to merge from upstream GCC into your repo, > rather than just dropping your repo into/onto a GCC clone, but to me > it seems the more natural solution. The modifications to the files in > the GCC tree would also be in your branch (and properly tracked in > git), and so not need to be done manually after untarring gm2 into the > GCC tree. > > It would mean your gm2 repo would contain the full GCC history, but > you said disk space isn't a concern. A checkout would need to check > out the full GCC tree as well, but presumably you need some way to > obtain that anyway if you're going to unpack/checkout/whatever the gm2 > repo inside the GCC tree.
Hello, awesome thank you - yes indeed the branch suggestion makes a lot of sense,
