{"thread":{"id":"35768","subject":"inconsistent include behaviour for core.sharedRepository","startedAt":"2014-01-30T18:52:38Z","lastAt":"2014-01-30T18:52:38Z","messageCount":1,"participants":["Gordon McGregor"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"233954","messageId":"CABJvL7duzsqH=3DLR6uhD05x2RmVJ=K53Up30K3sHOYzSfaLfw@mail.gmail.com","threadId":"35768","inReplyTo":null,"subject":"inconsistent include behaviour for core.sharedRepository","fromName":"Gordon McGregor","fromEmail":"gordon.mcgregor@nitero.com","sentAt":"2014-01-30T18:52:38Z","receivedAt":"2014-01-30T18:52:38Z","isPatch":false,"sender":{"key":"gordon.mcgregor@nitero.com","avatar":null},"body":"After several days of problems with directory permissions in the\nobjects/ directory for shared users, I finally found the cause of an\nissue that we have been seeing.\n\nWe are working with several shared repositories. We were trying to use\na shared [include] configuration that contained\n\n[core]\nsharedRepository = group\n\nThis was not being honoured, from an included config file.\n\nUsing git config, would show that core.sharedRepository was set to\n'group', as expected.\n\nHowever, digging through setup.c I see that shared_repository is\nactually configured using git_config_early(), which does not use the\ninclude mechanism that git_config()/ git_config_with_options() uses.\n\nThis is particularly difficult to debug given the git-config reports\nvalues that are not actually used internally.\n\nI think that git config should report the correct values, for features\nthat are accessed via git_config_early. Otherwise it is quite\ndifficult to understand the behaviour, without the source code.\n\n\n\ngit version 1.8.2.1 on CentOS release 5.6 (Final)\n\n\n-- \nGordon McGregor\n+1 512 577 9712\n"}]}