So I have isolated this behavior to at least Windows XP, maybe SP3. I installed the VisualSVN Server on a SBS 2003 box and again, I set the pre-commit hook to always error. Only this time it DID block all commits, as one would expect.
Is this a known bug? If not, Does this post suffice as a bug report submission? -jbstegman On Jul 8, 9:13 am, jbstegman <[email protected]> wrote: > Sorry, bad grammar... 'excepted' s/b 'accepted'. > > -jbstegman > > On Jul 7, 11:31 pm, jbstegman <[email protected]> wrote: > > > Product: VisualSVN Server Standard > > Version: 2.1.2 > > OS: Windows XP SP3 > > > I am trying to use a pre-commit hook to enforce the lock-modify-unlock > > model and I have run into a brick wall. It seems that the VisualSVN > > Server (or TortoiseSVN) is NOT responding properly to an error exit > > from the pre-commit hook. > > > To prove this to myself I created a pre-commit.cmd with the hooks > > manager that contained only one command: > > > exit /b 1 > > > If I understand this correctly, this should block any commits. Right? > > Instead, commits are still excepted. I'm I doing something wrong? > > > -jbstegman
