Junio C Hamano <gits...@pobox.com> writes: > Even though I did allude to ../project.gitconfig in the original message, I > think there should probably be an explicit syntax to name a path that is > relative to the root level of the working tree. People do funky things using > $GIT_DIR and $GIT_WORK_TREE to break the ".. relative to the config > file is the root level of the working tree" assumption, and also a repository > can have a regular file ".git" that points at the real location of the > directory > that has "config" in it, in which case its parent directory is very unlikely > to > be the root level of the working tree.
There is another reason why I suspect that it may make the resulting system more useful if we had a way to explicitly mark the path you used to safeInclude (by the way, we do not do dashes in names for configuration by convention) as referring to something inside the project's working tree. In a bare repository, we might want to grab the blob at that path in HEAD (i.e. the project's primary branch) and include its contents. -- 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
