[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: David Anderson <david.anderson_at_calixo.net>
Date: 2005-12-18 04:01:23 CET

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

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.