On Wed, Feb 9, 2011 at 5:42 PM, Johannes Sixt <j.sixt@xxxxxxxxxxxxx> wrote: > [Sorry, sent too early - fat fingers :-(] > > Am 2/9/2011 17:38, schrieb Johannes Sixt: >> Am 2/9/2011 17:27, schrieb Francis Moreau: >>> Hi ! >>> >>> I'd like to restrict access to one of my repos: the project tracked by >>> it has several directories: a/ b/ c/ and I'd like to allow only >>> modifications happen in b/ directory. >>> >>> I'm planning to use git hooks, not sure which one I should use: if the >>> check should happen at the commit or push time or both. > ... >>> I also tried: >>> >>> git diff-tree <oldref> <newref> -- ^b || exit 1 >>> >>> but it doesn't work. >> >> git diff-tree --quiet <oldref> <newref> -- b > > should do it; it sets the exit code. but does that work if a commit modify b/ and another directory ? > But don't you also want to inspect all commits between oldref and newref? Yes I want to inspect all commits in the range. > Someone could have modified the directory, and then reverted the > modification in a later commit. If these commits arrive in a single push, > the above code wouldn't notice this. I agree but I thought that git diff-tree would list all changes made between the 2 refs. Thanks -- Francis -- 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