Philip Martin <philip@codematters.co.uk> writes:
> > it was "svn up", the operation "A base" was the result of a "move
> > folder".
>
> It's like getting blood out of a stone! Why do you never describe
> things fully?
Yes.
Solo, you don't seem to realize that it's *normal* to spend an hour,
or several hours, writing a useful bug report. If you don't spend
that amount of time, then you're asking someone else to spend it.
This explains why people don't place a high priority on your reports.
You often don't do the preparatory work that would help someone write
a fix.
What's frustrating is that people on this list have told you over and
over exactly how to do it. List every command precisely, narrow
things down to a compact recipe where possible, show the exact input
and output, etc. You always leave out some of these steps: you might
remember to say the version number of Subversion, but forget to say
what command you ran. Instead of giving an exact transcript of what
you did, you try to write an English prose description of it -- even
though everyone here says that a prose summary is *less* useful than a
transcript.
You don't have to listen. You are free to write your bug reports any
way you want. But people will continue to ignore them until you take
the time to do it right. If you want some developer to put in hours
of debugging time, then you must be willing to spend a proportional
amount of time making the bug report easy to understand and reproduce.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 10 21:24:28 2003