On May 22, 2014, at 10:16, Dan Ellis wrote: >> The pre-commit hook script is only called if Subversion's internal checks >> already passed; if the internal checks fail, there's no reason to call the >> pre-commit hook script since the commit will fail regardless of the hook >> script's outcome. >> >> The internal check that failed in this case was that you asked Subversion to >> put a file into a nonexistent directory. > > I don't quite follow what the different checks would be as in this case the > only difference is --parents vs no --parents. Both I imagine do a path > existence check and in both cases the path doesn't exist.
You're telling Subversion to copy a file into a nonexistent directory. When you don't use --parents, that's an error, which Subversion reports to you, albeit cryptically. When you do use --parents, it's not an error, because Subversion will try to create the directory for you, but that fails because your hook script forbids it. > It would be nice if the SVN client, for case insensitive operating systems, > could automatically resolve these case issues. I really don't expect that to > happen as working on operating system-specific stuff isn't always the best > use of time (smaller audience, limited impact, etc.). At present, Subversion repositories are case-sensitive filesystems. It might be nice if it could be specified at repository creation time that a repository should be case-insensitive, but that capability does not exist today. > In lieu of this, I'm working on changing all our directory entries to > lower-case. Yeah, that's probably a good idea, or at least some predictable naming scheme.
