On Tue, Aug 22, 2017 at 11:10:52AM -0700, Stefan Beller wrote: > On Tue, Aug 22, 2017 at 8:33 AM, Heiko Voigt <hvoigt@xxxxxxxxxx> wrote: > > On Mon, Aug 21, 2017 at 09:42:54AM -0700, Stefan Beller wrote: > >> On Mon, Aug 21, 2017 at 9:05 AM, Heiko Voigt <hvoigt@xxxxxxxxxx> wrote: > >> > On Fri, Aug 18, 2017 at 11:51:13PM -0700, Junio C Hamano wrote: > >> # You feel the superproject is in the way? > >> git worktree add --for-submodule <path/to/sub> ... > >> # The new submodule worktree puts the > >> # submodule only UX first. so it feels like its own > >> # repository, no need for specific flags. > > > > I am not sure I understand this one. What would that do? Put a worktree > > for submodule path/to/sub to ...? > > Yes, and at "..." you would have the UX of the submodule being > its own repository, no interaction with the superproject. Are you sure that is what Junio meant? IMO that would be 'git worktree clone' or 'git worktree checkout', no? In todays git terminology an 'add' is something that puts data into the repository / the index. That is why I was/am confused. Cheers Heiko
