Re: svn commit: r1064093 - /subversion/trunk/subversion/libsvn_repos/authz.c
On 01/27/2011 10:26 AM, Mark Phippard wrote:
> On Thu, Jan 27, 2011 at 10:23 AM, C. Michael Pilato <cmpilato_at_collab.net> wrote:
>> We should probably release-note this change. It might be a rare situation,
>> but *if* folks have come to depend on the case-sensitivity of these checks,
>> they need to prepare for the fallout of this loosening of the policy.
> Can you envision a scenario where the current behavior works? I guess
> the only thing I can think of is if someone wanted a repository to
> just be read-only but incorrectly had it set to read-write and it was
> only not allowing the write because of case-sensitivity.
> This just seems like an obvious bug to me that anyone would have run
> into and changed their rules (to get the case right) until it worked
I'm not saying it's a common situation. I'm simply saying that it's better
to advise about this kind of thing up front rather than looking -- if only
to the 1 person in the world for whom it matters -- as if we didn't think
about the possible ramifications of the change.
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on 2011-01-27 17:41:17 CET
This is an archived mail posted to the Subversion Dev