On Friday, 9 December 2016 19:38:05 CET Duy Nguyen wrote: > >> Sounds like the same problem I have (and the reason I came up with > >> conditional include [1]). Would that work for you (check out the > >> example part in that patch)? > > > > If I understand correcly, I would need to set up config include in each > > git > > repository. This is as much work as setting up user.email in the same > > place. > > Well, no. You set this up in ~/.gitconfig. If you need to add some > settings in /abc/def/.gitconfig and expect repositories in this path > to reach it via the parent chain, then you could write something like > > [include "gitdir:/abc/def/"] > file = your-config-file > > in ~/.gitconfig and achieve the same effect, because all repos will > read ~/.gitconfig, and if it finds out the repo's location is inside > /abc/def, your-config-file will be loaded. It could contain email > settings or whatever. > > So, instead of spreading .gitconfig files around and relying on > parent-chain to reach them, you write a few filter rules in > ~/.gitconfig to tell all the repos what to load. oh... yes, that would solve my problem and have no impact on other user who don't need this feature. I do hope that the improvement you proposed will be merged. Thanks for the explanation. All the best -- https://github.com/dod38fr/ -o- http://search.cpan.org/~ddumont/ http://ddumont.wordpress.com/ -o- irc: dod at irc.debian.org