... | ... | @@ -91,7 +91,7 @@ tree! This is especially easy to mess up when creating new tests, so watch out. |
|
|
|
|
|
### Creating a buildtree with git-new-workdir
|
|
|
|
|
|
[ Since Git 2.9, \`git worktree\` works well enough with submodules](https://stackoverflow.com/questions/31871888/what-goes-wrong-when-using-git-worktree-with-git-submodules), so that the [ \`wtas\` alias](https://stackoverflow.com/a/31872051/388010) does what we want. If you can't get it to work, read on.
|
|
|
[ Since Git 2.9, \`git worktree\` works well enough with submodules](https://stackoverflow.com/questions/31871888/what-goes-wrong-when-using-git-worktree-with-git-submodules), so that the [ \`wtas\` alias](https://stackoverflow.com/a/31872051/388010) does what we want: `git clone --recursive git://git.haskell.org/ghc.git pristine && cd pristine/ && git wtas ../<feature-worktree>`. If you can't get it to work, read on.
|
|
|
|
|
|
|
|
|
I (ezyang) use Git workdirs to manage all of my GHC checkouts. It is quite nice: there is logically only one local repository, and just many checkouts of it, so it's very easy to share patches between various checkouts and your branches are all in one centralized place. However, sharing all of your submodules too takes a bit of work to setup, since Git doesn't natively support this workflow.
|
... | ... | |