Re: Able to mkdir .svn ?

"Francois Beausoleil" <fbeausoleil@ftml.net> writes:
> I was trying to think of special ways in which I could break SVN. I will
> write a test for that later, but here's a recipe that works:
>
> C:\>svnadmin create repos
>
> C:\>svn mkdir file:///repos/.svn -m "should not commit"
>
> Committed revision 1.

We actually decided that since the .svn directory is specific to our
working copy code, then only that code should protect against its
inclusion. So the above is legal (unwise, but legal).

We could offer a pre-commit hook to protect against it; that might
save some time for admins.

There was a long thread about this. I don't remember the subject
line, but it might have originated in an issue, so try searching the
issue tracker for something with ".svn" in the summary.

> Should I wait until I have create the test cases before submitting
> anything or messages like this are Ok ?

Oh, the message is fine, but of course we'd _always_ love a patch that
adds a new regression test -- that can save acres of time. Thanks for
asking.

-K

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 26 20:19:53 2003