On Jun 26, 2012, at 6:43 PM, Ryan Schmidt <subversion-20...@ryandesign.com> wrote:
> > On Jun 26, 2012, at 12:43, Mark Phippard wrote: > >> I cannot speak to all scenarios because I have not tested them. For >> example, if the svnsync user simply had no read access to anywhere in >> the repository it seems like it ought to error. But that scenario >> aside, the way that svnsync works is actually a huge feature. Imagine >> you have a remote team of contractors that you want to give a local >> replica of your repository. These contractors are not allowed access >> to parts of your repository. The contractors can use svnsync to crete >> a local replica using their credentials and their local repository >> will only contain the content they are allowed to access. The >> revisions that altered other paths will simply be empty commits. > > What happens if a single commit touches both paths that are allowed and paths > that are prohibit by a particular svnsync user? Will the entire commit be > ignored or will the parts of it that are in the allowed paths be included and > the rest removed? > The latter will happen. Mark
