On Wed, Dec 02, 2015 at 08:13:41PM +0100, Nguyễn Thái Ngọc Duy wrote: > Let's restart this. From the last discussion [1], we need to make > core.worktree per-worktree for submodules to work. We also need > core.sparseCheckout per-worktree.
Thank you. It would be nice to have it, so that features like submodules work fully. Now there are extensions support, would it make sense to mark repositories which use per-worktree config with an extension? It could clearly separate 2.5-style multi-worktree repositories (which might exist already around) from the new format. The extension could be set by 'worktree add' while creating first worktree, for example. > This series adds a pattern list, with .gitignore syntax mostly, that > split config var set into two sets, the per-worktree set will be > stored in .git/worktrees/*/config.worktree instead. The pattern list > consists of default patterns, built in git binary, and user ones in > .git/info/config.worktree. Using builtin defaults might be confusing for users - editing the info/config.worktree they must keep in mind the list of defaults (which they seem to don't know). Also, if anybody wants to extend the default list (like myself, for submodules), should they edit the info/config.worktree in provided template of extend the builtin list? What was wrong with the default in template? -- Max -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
