Francois Beausoleil wrote:
>Hi !
>
>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.
>
Ah! That's a good one.
>C:\>svn co file:///repos
>svn: Obstructed update
>svn: failed to add directory 'repos/.svn':
>object of the same name as the administrative directory
>
>C:\>svn version
>unknown command: version
>Type `svn help' for usage.
>
>C:\>svn --version
>svn, version 0.20.0 (r5410)
> compiled Mar 24 2003, 22:54:20
>
>Should I wait until I have create the test cases before submitting
>anything or messages like this are Ok ?
>
>
I think this is actually a pretty good bug report. It doesn't mention
the OS (although that's obvious from the format of your command line
prompt :-) but it does mention the version of SVN and give the exact
sequence of commands necessary to reproduce the problem. I wish all our
bug reports were like this...
Could you create an issue about this? Pasting your original
reproductieon recipe should be quite O.K.
--
Brane Čibej <brane_at_xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
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:16:19 2003