On Feb 23, 2007, at 02:29, Jan Hendrik wrote:
> Ryan Schmidt wrote on 22 Feb 2007, 15:02, at least in part:
>
>> Jan: Duncan meant you should provide a set of commands that anyone
>> could execute on their own machines to observe the problem. That
>> means you should start with the creation of an empty repository, and
>> go from there until you get the error. Like this script, which
>> demonstrates the problem:
>>
>>
>> # Create a new repo and check out a working copy
>> $ svnadmin create repo
>> $ svn co file://`pwd`/repo wc
>> Checked out revision 0.
>> $ cd wc
>
> [...]
>
> Thanks, Ryan, for this verbose example. As far as I can see you
> fully translated my report, only that I should test it here of course.
> Am I right in understanding that on *nix one would save this into a
> file and run? I don't think it would work out at all on Windows, that
> there usually isn't any "touch" or "ls" "cat" on Windows or "dir" on
> *nix aside. Sorry, I may sound dense, but this is absolutely new
> business to me.
Some people provide shell scripts that can be run to demonstrate a
problem. I'm wary of such scripts; I'd have to look into them myself
to see what they do before I'd trust them enough to run them anyway.
Myself, I like providing transcripts, including both the statements I
ran (preceeded with "$"), comments about what I'm doing (preceeded
with "#"), and the actual output of the commands. I think this way
it's clear to someone just quickly reading the message what the
output would be, without having to run it themselves.
I don't use Windows so I don't know what you would have to do to
reproduce the problem on that platform.
--
To reply to the mailing list, please use your mailer's Reply To All
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Feb 25 11:10:33 2007