>
> 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.  In the end, it
really doesn't matter - its a general curiosity on my part.

I agree the error message could be improved, as I said above. I can
> reproduce it with a simple script:
>
I agree, it lead me astray for a little bit.

I don't understand how you get into the situation of knowing the letters in
> the names of directories in the repository but don't know their case.
>
Time.  Developers know the project names and subsystems very well, but do
not always remember case, especially when we move from project to project.
 This is not a normal use case as most users will have a local WC checkout,
but we use this for some archival purposes where we don't really want every
developer with a checkout (one way trip stuff).

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.).  In lieu  of
this, I'm working on changing all our directory entries to lower-case.

Thanks for the help,
Dan

Reply via email to