Changes between Version 79 and Version 80 of WorkingConventions/Git


Ignore:
Timestamp:
Feb 15, 2018 1:56:52 PM (20 months ago)
Author:
sgraf
Comment:

git worktree specifics

Legend:

Unmodified
Added
Removed
Modified
  • WorkingConventions/Git

    v79 v80  
    9090=== Creating a buildtree with git-new-workdir ===
    9191
    92 [https://stackoverflow.com/questions/31871888/what-goes-wrong-when-using-git-worktree-with-git-submodules Since Git 2.9, `git worktree` works well enough with submodules], so that the [https://stackoverflow.com/a/31872051/388010 `wtas` alias] does what we want. If you can't get it to work, read on.
     92[https://stackoverflow.com/questions/31871888/what-goes-wrong-when-using-git-worktree-with-git-submodules Since Git 2.9, `git worktree` works well enough with submodules], so that the [https://stackoverflow.com/a/31872051/388010 `wtas` alias] 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.
    9393
    9494I (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.