Re: Fixed issue #1456, can this get into 1.3.0?

David Summers wrote:
> Is this serious enough to put in to 1.3.0 or should it just go into the
> normal bug fixes for 1.3.1?

My feel is that if people have lived with it for so long, and if it is not
critical (no dataloss, no security hole etc.), it should just go on the roster
for 1.3.1 . Unless there is a very strong feeling to the opposite.

- Dave

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Dec 18 04:02:03 2005