On Thu, Mar 19, 2015 at 4:33 AM, Max Kirillov <max@xxxxxxxxxx> wrote: > On Sun, Feb 08, 2015 at 09:36:43AM -0800, Jens Lehmann wrote: >> I wonder if it's worth all the hassle to invent new names. Wouldn't >> it be much better to just keep a list of per-worktree configuration >> value names and use that inside the config code to decide where to >> find them for multiple work trees. That would also work easily for >> stuff like EOL-config and would push the complexity in the config >> machinery and not onto the user. > > I actually thought about the same, and now tend to think > that most of config variables make sense to be per-worktree > in some cases. Only few variable must always be per > repository. I tried to summarize the variables which now > (in current pu) should be common, also listed all the rest > so somebody could scan through the list and spot anything I > could miss. Thanks for compiling the list. At this point I think it may not be sensible to hard code some config vars (e.g. core.worktree) to be local or shared. So I'm thinking (out loud) that we may have a file $GIT_DIR/worktrees/<id>/local-config-patterns (or some other name) that would define what vars are local. gitignore syntax will be reused for this. The file would provide more flexibility.. -- Duy -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html